Read more at: TechTarget

• Service-oriented architectures built upon open, standards-based Web Services provide a strategic IT direction businesses need to meet their fundamental business goal: agility.
• By 2010, ZapThink expects 69% of the total enterprise software market to be Service-oriented.
• The overall market for products and services that support Service orientation will be over $98 billion by 2010.
• Reworking existing brittle, high-cost IT infrastructures into flexible, Service-oriented architectures promises substantial long-term cost savings and revenue opportunities through increased business agility.
• Service orientation represents the latest distributed computing approach to affect IT — the fourth major shift since the mid-twentieth century.
• ZapThink predicts that companies will begin to accept Service orientation in 2003, and it will become the dominant distributed computing approach by 2006.

Table of Contents:

• I. Report Scope
• II. Context for Service-Oriented Architectures
  • 2.1. What is a Service-Oriented Architecture?
    • 2.1.1. Evolution of Distributed Computing
  • 2.2. Business Motivations for SOAs
    • 2.2.1. The Economics of Business Agility
• III. Foundations of SOA
  • 3.1. SOA Foundation: Model-Driven Architecture
  • 3.2. SOA Foundation: Agile Methodologies
  • 3.3. The SOA Metamodel
  • 3.4. The 4+1 View Model of SOA
• IV. Best Practices of SOA
  • 4.1. Develop a top-down, extended enterprise SOA
  • 4.2. Build & maintain a platform independent Service model
  • 4.3. Maintain feedback at all points of the architecture
  • 4.4. Follow Agile Methodology principles & techniques within the context of the Service model
  • 4.5. Encapsulate existing/legacy functionality
  • 4.6. Embrace heterogeneity/follow a federation model of software
  • 4.7. Compose atomic Services into coarse-grained business Services
  • 4.8. Build for consumability/broad applicability
  • 4.9. Perform ad hoc upgrades
  • 4.10. Prioritize SOA transition activities on the fly
• V. Market Segmentation
  • 5.1. Current State of the Market
• VI. Business and Technology Trends
  • 6.1. Long Term Trends: A Shift in the Favored Approach to Distributed Computing
  • 6.2. Long-Term Trends: Grid/Utility Computing
  • 6.3. Inhibitors to Growth of Service Orientation and SOAs
• VII. Conclusions
  • 7.1. Key Notes
  • 7.2. Decision Points
  • 7.3. Best Practices
  • 7.4. Figures
  • 7.5. Tables
  • VIII. Profiled Vendors

Download File

• Service-oriented architectures built upon open, standards-based Web Services provide a strategic IT direction businesses need to meet their fundamental business goal: agility.
• By 2010, ZapThink expects 69% of the total enterprise software market to be Service-oriented.
• The overall market for products and services that support Service orientation will be over $98 billion by 2010.
• Reworking existing brittle, high-cost IT infrastructures into flexible, Service-oriented architectures promises substantial long-term cost savings and revenue opportunities through increased business agility.
• Service orientation represents the latest distributed computing approach to affect IT — the fourth major shift since the mid-twentieth century.
• ZapThink predicts that companies will begin to accept Service orientation in 2003, and it will become the dominant distributed computing approach by 2006.

Table of Contents:

• I. Report Scope
• II. Context for Service-Oriented Architectures
  • 2.1. What is a Service-Oriented Architecture?
    • 2.1.1. Evolution of Distributed Computing
  • 2.2. Business Motivations for SOAs
    • 2.2.1. The Economics of Business Agility
• III. Foundations of SOA
  • 3.1. SOA Foundation: Model-Driven Architecture
  • 3.2. SOA Foundation: Agile Methodologies
  • 3.3. The SOA Metamodel
  • 3.4. The 4+1 View Model of SOA
• IV. Best Practices of SOA
  • 4.1. Develop a top-down, extended enterprise SOA
  • 4.2. Build & maintain a platform independent Service model
  • 4.3. Maintain feedback at all points of the architecture
  • 4.4. Follow Agile Methodology principles & techniques within the context of the Service model
  • 4.5. Encapsulate existing/legacy functionality
  • 4.6. Embrace heterogeneity/follow a federation model of software
  • 4.7. Compose atomic Services into coarse-grained business Services
  • 4.8. Build for consumability/broad applicability
  • 4.9. Perform ad hoc upgrades
  • 4.10. Prioritize SOA transition activities on the fly
• V. Conclusions
  • 5.1. Key Notes
  • 5.2. Decision Points
  • 5.3. Best Practices
  • 5.4. Figures
  • 5.5. Tables
  • VI. Profiled Vendors

Download File

• Service-oriented architectures built upon open, standards-based Web Services provide a strategic IT direction businesses need to meet their fundamental business goal: agility.
• By 2010, ZapThink expects 69% of the total enterprise software market to be Service-oriented.
• The overall market for products and services that support Service orientation will be over $98 billion by 2010.
• Reworking existing brittle, high-cost IT infrastructures into flexible, Service-oriented architectures promises substantial long-term cost savings and revenue opportunities through increased business agility.
• Service orientation represents the latest distributed computing approach to affect IT — the fourth major shift since the mid-twentieth century.
• ZapThink predicts that companies will begin to accept Service orientation in 2003, and it will become the dominant distributed computing approach by 2006.

Table of Contents:

• I. Report Scope
• II. Context for Service-Oriented Architectures
  • 2.1. What is a Service-Oriented Architecture?
    • 2.1.1. Evolution of Distributed Computing
  • 2.2. Business Motivations for SOAs
    • 2.2.1. The Economics of Business Agility
• III. Foundations of SOA
  • 3.1. SOA Foundation: Model-Driven Architecture
  • 3.2. SOA Foundation: Agile Methodologies
  • 3.3. The SOA Metamodel
  • 3.4. The 4+1 View Model of SOA
• IV. Market Segmentation
  • 4.1. Current State of the Market
• V. Business and Technology Trends
  • 5.1. Long Term Trends: A Shift in the Favored Approach to Distributed Computing
  • 5.2. Long-Term Trends: Grid/Utility Computing
  • 5.3. Inhibitors to Growth of Service Orientation and SOAs
• VI. Conclusions
  • 6.1. Key Notes
  • 6.2. Decision Points
  • 6.3. Best Practices
  • 6.4. Figures
  • 6.5. Tables
  • VII. Profiled Vendors

Download File

• Service-Oriented Integration (SOI) simplifies system integration by providing a single, simple architectural framework based on Web Services in which to build, deploy, and manage application functionality.
• The SOI market is expected to grow from $435 million in 2001 to about $6.2 billion in 2006.
• The top three EAI vendors have over 43% of the overall EAI market. With the entrance of Microsoft and other vendors in 2002, this landscape is expected to change.
• Web Services isn’t an integration technology, but a distributed computing technology that lends itself well to being used in integration scenarios.
• In a Web Services context, there really is no difference between EAI, B2Bi, and Data Integration.
• SOI solutions allow users to get a greater level of interaction and granularity with components deep within the application.
• SOI faces challenges in immature specifications, insufficient reliability, security, and transaction control.
• Microsoft and IBM have made strong entries into this space that will be a challenge for other providers of SOI solutions.
• The potential ROI realized by adopting Service-Oriented Architectures (SOA) far outweighs the slight benefits an organization gets from using Web Services as simply a “better API” for accessing application functionality.
• Integrating systems between two businesses is not only a technological problem; it requires pre-existing business relationships between the companies.

Table of Contents:

• I. Report Scope
• II. Integration: The Challenges to be Solved
  • 2.1 The N-Squared Integration Challenge
  • 2.2 Classes of Integration Problem
  • 2.3 Traditional EAI and B2Bi Solutions
  • 2.4 Why Current EAI and B2Bi Solutions are Not Sufficient
  • 2.5 The Integration “Zipper”
• III. Service-Oriented Integration Approaches
  • 3.1 Using Web Services for Integration: Service-Oriented Integration (SOI)
  • 3.2 Methods for Implementing SOI
  • 3.3 SOI-enabled EAI and B2Bi Solutions
  • 3.4 Emerging SOI Solutions
  • 3.5 Data-focused SOI Solutions
• IV. Drivers for SOI Adoption
  • 4.1 Reduce the cost and complexity of managing IT infrastructures
  • 4.2 Provide a uniform platform for B2B exchange and marketplaces
  • 4.3 Move away from proprietary technologies and solutions
  • 4.4 Enable application and data reuse
  • 4.5 Simplify business modeling
  • 4.6 Provide fine-grained access to data, functionality, and logic
• V. ROI for Service-Oriented Integration
  • 5.1 TCO and ROI of Traditional EAI and B2Bi Solutions
  • 5.2 Improving the ROI Outlook with SOI
  • 5.3 The Movement to the “Agile Enterprise” Offers Greatest ROI
  • 5.4 Realize Integration ROI Internally First, Externally with Trusted Parties Second
• VI. Barriers and Challenges to SOI Adoption
  • 6.1 Interoperability of SOI implementations
  • 6.2 SOI specifications are far from complete
  • 6.3 SOI can require the re-architecting of systems
  • 6.4 Lack of Semantic Integration
  • 6.5 Web Services introduces its own level of complexity and inefficiency
• VII. Market Size and Future Trends
  • 7.1 The Convergence of EAI, B2Bi, and Data Integration Markets
  • 7.2 Market Opportunity and Sizing
  • 7.3 Current Vendor Positioning and Market Share
  • 7.4 Future Directions for Service-Oriented Integration
• VIII. Conclusions
  • 8.1 Key Notes
  • 8.2 Decision Points
  • 8.3 Figures
  • 8.4 Tables
• IX. Profiled Vendors
  • 9.1 SOI-enabled Web Services Platforms
  • 9.2 SOI-enabled EAI and B2Bi Solutions
  • 9.3 Emerging SOI Solutions
  • 9.4 Data-Focused SOI Solutions
• A. Related Research
  • Reports
  • Briefing Notes
• B. Supporting Resources
• C. Trademark Notice and Statement of Opinion
• About ZapThink, LLC

Download File

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best practices as well as an analysis of the tools that are currently available for building Service-oriented architectures.Download File