Building an enterprise-scale software system is a complex undertaking. Despite decades of technological advances, the demands imposed by today’s information systems frequently stretch to breaking point a company’s ability to design, construct, and evolve its mission-critical software solutions. In particular, few new systems are designed from the ground up. Rather, a software architect’s task is commonly that of extending the life of an existing solution by describing new business logic that manipulates an existing repository of data, presenting existing data and transactions through new channels such as an Internet browser or handheld devices, integrating previously disconnected systems supporting overlapping business activities, and so on. To assist software developers, commercial software infrastructure products are now available from vendors such as Microsoft and IBM. They form the centerpiece of the approaches to software development they advocate in their .NET and WebSphere product lines, respectively. Both approaches focus on assembly of hsystems from distributed services. However, is there anything new about building enterprise-scale solutions from services? How do the lessons of component-based systems apply to construction of service-based architectures (SOA)? What are the best approaches for building high quality systems for deployment to this new generation of software infrastructure products? These important questions are the topic of this paper
Click here
Contents.........................................................................................................................................................2 Introduction...................................................................................................................................................2
What Is a Service-Oriented Architecture?......................................................................................................3
Interface-Based Design.............................................................................................................................5
Interface Behavior.................................................................................................................................5
Architecting Service-Oriented Systems..........................................................................................................6
Layering Application Design..................................................................................................................6
Example Customer Model......................................................................................................................7
A Component-Based Design......................................................................................................................8
A Service-Oriented Design.........................................................................................................................8
Caching in Service Oriented Design.......................................................................................................9
XML Web Services Application Design......................................................................................................10
Web Service Design and Implementation Patterns...................................................................................11
Performance and Reliability.................................................................................................................11
Scalability Through Asynchronous Behavior and Queuing.................................................................12
Information Leasing Revisited.............................................................................................................13
Resulting Web Service Design Model......................................................................................................14
Objective is to keep track of what all I am working on at the moment.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment