SOA Down to Earth: What You Should and Shouldn't Do to Make It Happen

Transcription

1 SOA Down to Earth: What You Should and Shouldn't Do to Make It Happen Notes accompany this presentation. lease select Notes age view. These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e mail vendor.relations@gartner.com. Massimo ezzini

2 SOA in the Trough of Disillusionment: Bad News or Good News? Application Integration & latform Middleware Hype Cycle, 2006 visibility ackaged Integration Business Activity Monitoring Web Services Management Service Registry Integration Repositories Extensible Microkernel Style latforms Event Driven Architecture Alternative Open Source Application latforms Business rocess Networks Vocabulary Based Transformation Event Based Application latforms Distributed Caching latforms Grid Based Application latforms Service Component Architecture Enterprise Service Bus Managed File Transfer B2B Gateway Software XML Appliances Advanced Web Services SOA resentation Integration Servers Integration Competency Centers J2EE rogrammatic Integration Servers Basic Web Services Integration Service roviders Microsoft.NET Application latform Integration Suites Open Source J2EE Enterprise Scope Application latform Suites Technology Trigger eak of Inflated Expectations Years to mainstream adoption: Trough of Disillusionment time Slope of Enlightenment less than 2 years 2 to 5 years 5 to 10 years more than 10 years As of July 2006 lateau of roductivity obsolete before plateau

3 Key Issues 1. Why should organizations adopt SOA? 2. What are the critical phases organizations will go through to get to enterprisewide SOA? 3. Which are the key hurdles on the way to SOA, and how can organizations get over them?

4 Why Service Oriented Architecture? Business Drivers revail Over IT Drivers M & A/Divestitures Multichannel sales/support Time to market Continuous innovation rocess flexibility rocess visibility "Top Down" Enterprise Drivers SOA "erennial" IT Challenges "Doing more with less" Business/IT alignment Data consistency/quality Time to deployment Call center integration Single face to clients, suppliers, employees rocess Integration Real time B2B "Bottom Up" Business Unit Drivers

5 Beyond the SOA Hype: What's for Real? Benefits Architectural artitioning Diverse life cycle "speeds" Synergy of different technologies Optimal tech skills allocation rocesses visibility Greater maintainability Easier outsourcing/offshoring Incremental Deployment Gradual migration Cost "spreading" across projects Reduced maintenance cost Sharing (Reuse) of Services: Faster time to deployment Lower development cost Greater adaptability Common "Language" Between Business and IT Implications Higher Upfront Costs Cultural change Infrastructure (SOA backplane) More formal methodology Longer design time for services Testing (unit/end to end) More Distributed Infrastructure Extensive use of middleware Transaction management Debugging/troubleshooting End to end management More granular security Metering/logging Tighter Management/Governance Ownership/accountability Cost allocation rioritization/conflict resolution

6 Strategic lanning Assumption Through 2008, the upfront investment for large scale service oriented applications will be justifiable only for projects with a planned lifetime of three years or more (0.8 probability).

7 ackaged Business Applications and SOA: An Inevitable Marriage ackaged Applications Vendors Approach to SOA re SOA Era re 2006 Monolithic ackaged App roprietary MW ropritary AIs HTT/IIO/DCOM Wrapped SOA 2006 Monolithic ackaged App Standard base MW Web Services Interfaces SOA Era Intermediate Steps Service Regustry/ Repository Enterprise SOA Circa 2010 Native SOA ackaged App SOA Enabling MW Enterprise Service Bus Composite Applications Composite Applications Composite Applications

8 Key Issues 1. Why should organizations adopt SOA? 2. What are the critical phases organizations will go through to get to enterprisewide SOA? 3. Which are the key hurdles on the way to SOA, and how can organizations get over them?

9 Stages of SOA Adoption Stage 1 Introduction Stage 2 Spreading Stage 3 Exploitation Stage 4 lateau Business Goals IT Goals Scope Address Specific ain (e.g., Customer ortal) roof of Concept Single Application rocess Integration (e.g., B2B) Establish Technology latform Multiple Applications (Single BU) rocess Flexibility (e.g., Time to Market) Leverage Services Sharing Multiple Applications (Cross BUs) Continuous Adaptation & Evolution Enterprise SOA Infrastructure Virtual Enterprise No. of ublished Services* No. of Service Consumers* No. of Service Calls/Day* No. of Service Developers* <25 <100 <500 >500 <5 <25 <50 >50 <10,000 <100,000 <1,000,000 >1,000,000 <10 <20 <100 >100 Enabling Technology (cumulative) Application Server, ortal, Adapters ESB, WSM Integr. Suite, B2B SOA Reg/Rep BM olicy Mgmt. Enterprise SOA Backplane * =These figures represent typical scenarios, but they may vary considerably depending on the specific organization's requirements.

10 Which Stage of SOA Adoption Are You Ready For? Required Management Buy in Required Skills Required Organizational Capabilities = Imperative = Recommended Head of Development or Head of Integration CTO/Head of Architecture Stage 1 Introduction Stage 2 Spreading Stage 3 Exploitation Stage 4 lateau O X X Head of IT Operations O CIO/Business Units O X CEO O X Basic Middleware Web Services Integration Middleware O X Service Oriented Development of Applications (SODA) O X Business rocess Management O X SOA Operations Management O X SOA Center of Excellence O X Service Life Cycle Management O X Service Design Methodology O X lanning Control and Quality Management O X Service Reuse Methodology O X Operation Management O X Domains O X Cost Allocation Schema O X Consistent Enterprisewide Governance rocesses O X Enterprisewide SOA Backplane O X

11 Strategic lanning Assumption Through 2010, fewer than 25% of large companies will have developed the technical and organizational skills needed to deliver enterprisewide SOA (0.8 probability).

12 Key Issues 1. Why should organizations adopt SOA? 2. What are the critical phases organizations will go through to get to enterprisewide SOA? 3. Which are the key hurdles on the way to SOA, and how can organizations get over them?

13 SOA Enabling Established Applications Wrapping Use of screen scraping to package "pseudo services" Re engineering Business logic is modularized and separated from presentation Introduction Replacement Business logic of services is redesigned from scratch or replaces with packages. Data Model Data Model Data Model Mixed Business Logic and resentation Logic Business Logic Business Logic Wrapper Interface Wrapper Interface ros: Noninvasiveness Low cost/fast Cons: Suboptimal granularity Hard to maintain resentation Logic Orchestration Interface Orchestration Interface ros: Easier to maintain Better performance/scalability Cons: Invasive/high cost Granularity might be suboptimal Orchestration Interface Orchestration Interface ros: Optimal granularity/reuse Enables technology change Cons: Risk is higher High cost

14 SOA and WSDL Are Not Enough: Orient Yourself Through the Middleware Bazaar Native SOA Application E AS Spreading Non SOA Wrapped Application Services Application Logic TM, EAS Wrapper Wrapper Wrapper Interface Interface Interface ESB, MOM, ORB, TM, IBS, Applicances ortal roduct, SES Multichannel ortal SOA Backplane Composite Application BM Application Adapters, rogrammatic Integration Servers BM Suite, IBS ortal roduct, EAS, resentation Integration Server

15 Flow Management in SOA: One Size Doesn't Fit All Microflows Orchestration Long Running rocess Spreading Workflow Goal Implement coarse grained services by executing flows of software components Scope Single application Key Features Subsecond execution cycle Transaction support Usually nondistributed, single platform State is not persisted Goal Implement coarsergrained services by orchestrating finergrained services Scope Usually single domain Key Features Subsecond to minutes execution cycle Compensation flows (automated or manual) Distributed/multiplatform State may or may not be not persisted Goal Automate business processes involving multiple services Scope Single/multiple domains Key Features Minutes to hours execution cycle Compensation flows (automated or manual) Distributed/multiplatform State must be persisted Goal Automate business processes involving human tasks and services Scope Single/multiple domains Key Features Minutes to months execution cycle Compensation flows (automated or manual) Distributed/multiplatform State must be persisted

16 How Do You Enforce Sharing of Services? "Bad" SOA "Good" SOA Exploitation Services Services Services Services Metrics # Services/# Consumers >>20 # of reused services <10% otential Issues: Too fine services granularity Duplicated services Over specified SOA Service Definition rocess Service Registry Rewarding olicies Service "Chasing" Team

17 Managing Life Cycle in SOA: The Service Registry Governace and Cost Allocation Definition and Validation Exploitation Development and Maintenance User Interface Replication and Federation Meta Registry Adapters Service Configuration and Dependency Versioning and Subscription Service Registry Discovery, Location, Management and Security

18 Enterprisewide SOA Is Multiowned and Multilayered SOA Domain "C" lateau Domain Registry Domain SOA Backplane SOA Domain "B" Enterprise SOA Backplane SOA Domain "A" Local Services Domain SOA Backplane Domain Registry Local Services Domain SOA Backplane rivate service = consumed by one application Enterprise Registry Local service = consumed by more applications in the same SOA domain ublic service = consumed by more applications from multiple SOA domains Domain Registry Local Services ublic Services

19 Recommendations Endorse SOA to be able to respond to business and IT challenges. SOA is not only about Web services. Build knowledge about middleware and application integration technologies as well. SOA is a journey. lan for multiyear incremental implementation steps, but look for short and medium term payback. Avoid a "wild" proliferation of services. Establish processes focused on maximizing reuse. Beware of SOA "extremism." SOA principles should be applied with a grain of salt.

20 SOA Down to Earth: What You Should and Shouldn't Do to Make It Happen Notes accompany this presentation. lease select Notes age view. These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e mail vendor.relations@gartner.com. Massimo ezzini

21 SOA Down to Earth: What You Should and Shouldn't Do to Make It Happen Notes accompany this presentation. lease select Notes age view. These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e mail vendor.relations@gartner.com. Massimo ezzini