SOA Scenario: Patterns and Guidelines for Starting With SOA ...


Published on

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SOA Scenario: Patterns and Guidelines for Starting With SOA ...

  1. 1. SOA Scenario: Patterns and Guidelines for Starting With SOA and Moving to Advanced SOA Anthony Bradley Notes accompany this presentation. Please select Notes Page view. These materials can be reproduced only with written approval from Gartner. Such approvals must be requested via e-mail: Gartner is a registered trademark of Gartner, Inc. or its affiliates.
  2. 2. SOA – Proven Transformative Power According to Gartner Research and 2008 SOA survey: SOA Emerging From Trough of Disillusionment • Mainstream companies are gaining SOA value - Business agility benefits in over 60% of respondents - Over 50% experienced dev productivity benefits - Over 40% gained sharing benefits • Some SOA success doesn’t mean all SOA success - Still a large number of SOA disappointments - Not “SOA bad” but “bad SOA” • Leaders and architects must understand SOA benefits and how to get there From "Hype Cycle for Application Architecture, 2008“ 3 July 2008 (G00159029)
  3. 3. Key Issues 1. What is SOA and how can it deliver value? 2. What are and will be the prevailing software patterns in SOA? 3. How does IT modernization contribute to SOA? 4. What are the emerging software development practices and their affinity with SOA?
  4. 4. SOA Fundamentals • SOA is an architectural approach to building systems Gartner’s Five Criteria for a SOA Application • delivering 2 major categories of value 1. Modular - Sharing (also called leverage and reuse) 2. Distributed - Agility (ability to change more 3. Discoverable rapidly) 4. Swappable • through 2 fundamental principles 5. Shareable - Interface Abstraction - Modularization
  5. 5. The Gartner SOA Business Case Framework The goal is to understand, identify and assemble SOA value information to create a business case document. Components of the Framework Business Case Document 1. Elements (30) describe fundamental SOA value Justification propositions and cost areas. 2. Elements are chained together for end-to-end traceability. Profiles 3. Chains are grouped into bundles according to the nature of the SOA project. Bundles 4. Each element has a descriptive profile. Chains 5. Chains and bundles assemble relevant element profiles into SOA justification. Elements
  6. 6. Elements Capture SOA Characteristics Traceability Traceability 6. SOA Principles 6. SOA Principles 3. SOA Technology Benefits 3. SOA Technology Benefits 2. SOA Business Benefits 2. SOA Business Benefits 1. Business Impact 1. Business Impact Modular Standardized Systems Integration Standardized Systems Integration Business Process Agility Business Process Agility Revenue Growth Revenue Growth Modular Faster Application Development Cost Reduction or Avoidance Market Share Swappable Swappable Faster Application Development Cost Reduction or Avoidance Market Share Enhanced Functionality Evolve-ability Time to New Capability Growth Enhanced Functionality Evolve-ability Time to New Capability Growth Shareable Shareable Improved Systems Deploy-ability Business Scalability Improved Systems Deploy-ability Business Scalability Better Profitability Better Profitability Clearly Defined Clearly Defined Improved Systems Scalability Improved Systems Scalability Increased Business Coordination Increased Business Coordination Competitive Competitive Distributable Better Process Visibility Enhanced Information Quality Distributable Better Process Visibility Enhanced Information Quality Position Position Discover Functionality Retirement 4. Costs/Risks Discover Functionality Retirement 4. Costs/Risks Regulatory IT Modernization and Business Process Management Regulatory IT Modernization and Technology Refresh Business Process Management Compliance Compliance Technology Refresh Cost Increases Legacy Systems Extension Cost Increases Legacy Systems Extension Business Operations Impact Enhanced Capability Sharing Business Operations Impact Enhanced Capability Sharing Organizational Culture 5. Costs/Risks Organizational Culture 5. Costs/Risks Services Governance Services Governance Information Security Information Security Systems Management Provides a framework for Provides a framework for Systems Management End-to-End Performance End-to-End Performance targeting application challenges targeting application challenges Architecture Effort Architecture Effort as SOA opportunities as SOA opportunities Skills Available Skills Available Technology Maturity Technology Maturity Organizational Capabilities Organizational Capabilities
  7. 7. The SOA Application Pattern Taxonomy Driven by open- Encapsulated (opaque) Separately-defined formal ended event published software services service interfaces notifications Software as Business Services Driven by named requests for work SOA Request-driven Event-driven IDL-based interfaces SOA SOA RPC WOA MQ Pub/Sub WS-* or Web SOAP Services Web Web Services Services RESTWeb-based interfaces Message-style WS-Reliable WS-Notification Event-object style interfaces Messaging or WS-Eventing interfaces
  8. 8. What Is Web-Oriented Architecture (WOA)? • Sub-style of SOA The Hourglass Model of Middle-Out Architecture • WOA=SOA+www+REST • Fundamental REST principles: Uncertainty Any Web user - Identification of resources Generic - manipulation of resources Systems Extensible through representations Generic - hypermedia as the engine of SimpleIdentifier: URL application state Format: Atom Interface Protocol: - self-descriptive messages HTTP - application neutrality • Web Federated Components - HTTP: Get, Post, Put, Delete PUT GET Uncertainty - URL addressability Any Web resource - No session state
  9. 9. Advanced SOA: Events, Requests and State Logical Unit of Work Start End Request Event Event Handler Notification Handler Business Process
  10. 10. Advanced SOA Initiatives Require Sophisticated Infrastructure: The SOA Backplane All-in-One Application Platform Suite Native SOA Application Non-SOA Wrapped Application Services Application Logic Wrapper Wrapper Wrapper TPM, EAS Interface Interface Interface SOA Backplane Adapters, ESB, IS, Programmatic Appliances Integration Servers BPM BPM Technology Application Portal Product Multichannel Composite Application/ Portal Product, EAS, Portal Mashup Composite Application Tools, Mashup tools
  11. 11. SOA Without Governance (aka Degenerating SOA) "Wild West" SOA Shelfware SOA Duplicated SOA • The most common case • A working SOA is • Slightly more disciplined and of a degenerated SOA. implemented, but more devious version of a • Services proliferate few applications Wild West SOA. wildly because no actually use the • Simply too large; may formal service definition public services. contain more than 1,000 process is in place. • Most applications remain services. as they are. • Although "things work well," • Frequently fueled by many services have widespread enthusiasm • There's little buy-in significant unplanned about the ease-of-use from several business duplication of Web services. units, no agreed-on • Rewarding mechanisms for • No central registry; application architecture creating reusable services nobody knows how companywide and and reusing established many services are reuse is an unkept services are vague. in place, where they promise. • Little reuse and are or what they do. • The intentions are maintenance costs multiply. • Extremely difficult good, but SOA is a • Companies are often situation to fix and waste of resources reasonably happy with this gain control of. and won't deliver SOA, even though their benefits. savings would multiply if they reduced the level of duplication.
  12. 12. Main RACI Table for SOA Governance Decision Responsible Accountable Consulted Informed Process Owners, Which services Enterprise Architects, Enterprise Application Developers, All CoE to do? Application Developers Architects Security Experts,** DB Experts** Enterprise Architects, Enterprise Process Owners, Application Developers, Architects, Which services Application Developers, All CoE, SOA CoE Internal Marketing, CoE Internal to do first? Security Experts,** Project Sponsor Process Owners, Marketing, DB Experts** SOA Project Sponsor* Process Owners If a new, reusable Application Developers, Enterprise Architects, Enterprise service is agreed, Is this really a Process Owners,* CoE Administrators, Architects, all CoE; if not, new, reusable Integration Tech. Vendors,* Application Developers, CoE service owners service? Security Experts,** Process Owners* Administrators of the services DB Experts** that are reused. Who's going to Enterprise Architects, SOA Project Process Owners, pay for the Application Developers, Application Process Owners, Sponsor, development & Operations, Developers, Application Developers, IT Budget maintenance Security Experts,** Service Owners IT Budget Committee Committee of this service? DB Experts** Enterprise Process Owners, Enterprise Architects, Architects, Application Developers, Who owns Application Developers, Application Operations, All CoE this service? Process Owners* Developers, Security Experts,** Process Owners* DB Experts** * For coarse granularity, highly reusable services ** Depending on the nature of the service
  13. 13. IT Modernization – A Flight to Flexibility Is IT helping to improve business results in existing markets? Is IT producing the right level of performance at a competitive price?” Can IT help the business move to new markets ?
  14. 14. The Pace of Change for Modernization IT Drivers Market Drivers • Staffing, Skills • Social Networking • Consolidation • Consumerization • Agility/need for speed • Green Business Technology Drivers • Virtualization is everywhere • SOA Initiatives • Facilities and Infrastructures • Packaged Applications
  15. 15. IT Modernization – The Domino Effect Finding and fixing the Dominos • Trinity Millennium Group • BluePhoenix • Speedware • HP • Microsoft • Micro Focus • Oracle • TSRi Aging IT infrastructures and applications, coupled with an increased need to be responsive to business demands have forced many organizations to rethink traditional incremental technology improvement programs and focus on 14 a holistic IT Modernization program.
  16. 16. Software Development: The Future is Now •~250 Billion lines of legacy Long-term Impact of Short-term Actions code, 200 million lines of Cobol. •The Services being built today will last for…. •>10K Facebook Applications, Force.Com, Amazon Web Services are available today
  17. 17. Gartner's Maturity Model for Application Organizations Level 1 Level 2 Level 3 Level 4 Level 5 Ad Hoc Repeatable Defined Quantitatively Optimizing Managed High • Process limitations • Measures recognized indicate • Clear process improvement • Processes performance responsibility defined and • Identifies assigned Maturity documented gaps • Consistently, • Consistently • Automated reliably and • Teams followed process regularly • Processes establish across the generates improves not specified processes organization data for based on • Individuals • Repeatable • Little rework measures measures determine within team • Synergy • Interdepend- • Interdepend- • Reinvent • Little cross- among ency among ency among Low wheel each discipline disciplines disciplines disciplines is time activity strengthens emerges essential
  18. 18. APPLES VERSUS ORANGES Legacy Versus New Dev Platforms, circa 2010 Senior Amazon Developer Java EE Web Google Services App Engine VB.Net Junior Dev LAMP VB6 (PHP, RoR) Yahoo Pipes Excel with Google Power Microsoft Macros Popfly Docs? User Legacy Hybrid or New Apps Mashed Up Apps
  19. 19. Recommendations ü Treat SOA as a strategic initiative. ü Justify and measure SOA success ü Use a systematic approach to designing services for particular and extended use. ü Advance gradually through SOA stages of maturity. ü Establish a competency center to coordinate SOA efforts. ü Address SOA as part of an IT modernization effort ü Explore new development methods to achieve the agility and sharing benefits of SOA