Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Establishing SOA Focused Enterprise Architecture

799 views

Published on

 
Enterprise architecture frameworks (i.e. TOGAF) define data, application, technology, and business domains. Where do services, APIs , and streams fit into the blueprint? Teams can enhance architectural integrity and coherence by establishing a SOA-focused and API-centric foundation for their architecture efforts. In this presentation, Chris will describe key Enterprise Architecture patterns and practices that accelerate project delivery and create a SOA-focused architecture. During this session, you will learn:

Why SOA-focused Enterprise Architecture and API-centric approaches accelerate project delivery and increase
What patterns and practices help overcome common SOA and Enterprise Architecture challenges
How to fit project-oriented service development into an Enterprise Architecture picture

Published in: Software
  • Be the first to comment

Establishing SOA Focused Enterprise Architecture

  1. 1. Establishing SOA-focused Enterprise Architecture Chris Haddad VP Platform Evangelism WSO2
  2. 2. Bermuda Triangle of Architecture Enterprise Architecture API-centric Architecture Service Oriented Architecture
  3. 3. Why Architecture Matters “Manage the complexity of the IT environment and applies principles and techniques to reduce the complexity, improve efficiencies, and reduce capital and operational expenditure.” • Integrity and Coherence Simplifies Project Execution • Portfolio and System-of-System Views Decrease Inefficiencies • Architecture Catalog Improves Productivity and Agility
  4. 4. Enterprise Architecture Focus
  5. 5. Enterprise Architecture Challenges • Scope – Project versus portfolio view – Little interest in consuming shared services and standard platforms • Collaboration – Separate team or embedded agents – Poor visibility into projects • Execution – Short project development cycles – Can you Build from the Blueprint
  6. 6. Fit services, APIs , and streams fit into the blueprint
  7. 7. Service Oriented Architecture
  8. 8. Service Oriented Architecture Focus • Loose Coupling – Be permissive in what you accept – Separate interface from implementation • Separation of Concerns – Identity bridging – Publish coarse grained, message-oriented interfaces • Service-orientation – Achieve progress in portfolio breadth, depth, and adoption – Publish standard data models (80/20 rule)
  9. 9. Is Your Enterprise SOA Solving IT Challenges? • Potential consumers do not trust service stability, reliability, availability, or performance • Providers have scalability concerns and lack an ability to manage consumption • Security risks prevent publishing and offering open access • Difficult to manage requirements from multiple consumers and coordinate release schedule • Inability to configure service per consumer • Business return requires service metering usage rates, and billing
  10. 10. API-centric Architecture Focus • Business Building Blocks • Developer Adoption • A Simple Facade
  11. 11. Separate Internal from External 11 APIs API Façade Services Services Services BU-1 BU-2 BU-3
  12. 12. Implement an API Facade
  13. 13. Present a Portfolio View
  14. 14. API-Centric Architecture Challenges • API design • REST/JSON to SOAP/RPC message format translation • Identity Integration • Contextual Personalization – SLA, access privileges, monetization
  15. 15. 1 Big Data Stream Platform
  16. 16. Scalable Big Data Stream Deployment
  17. 17. Building the Reference Architecture Solution
  18. 18. Business Services Platform : Component Architecture
  19. 19. Business Service Platform : Layered Architecture Integration Layer - 1 Datamodel Integration Layer - 2 Services Platform Datamodel Data Layer Business Services
  20. 20. Integration Building Blocks • Promotion and Collaboration – Landing page or API Store • Communication, updates • Self-service support and direct support • Research and Development Product Ideas, Opportunities, and Labs • On-boarding API developers and consumers – On-demand registration and key generation – Documentation and Resources – Provide a Last Mile On-Ramp • Interoperable interface • Tools, Mobile client SDK, Authentication, Shared Platform
  21. 21. Integration Building Blocks • Delivery – Security and Quality of Service at Scale – Deployment Environments • Measuring Business Value – Usage, SLA management, version control, re-use – Monetization
  22. 22. Actualizing the Enterprise SOA Architecture • Publish service catalogue and service tiers • Incorporate demand and capacity management • Govern lifecycle management and workflow • Continuous provisioning and deployment • Enforce Service level management • Establish Collaboration channels
  23. 23. Level 0 – SOA-Focused Enterprise Architecture
  24. 24. Level 0 – SOA-Focused Platform
  25. 25. Enterprise SOA and API Integration Platform
  26. 26. L1 (Level 1) – Enterprise Architecture
  27. 27. Run Time View
  28. 28. WSO2 Advantage • Configuration driven • Pattern driven • Decoupled architecture
  29. 29. Recommended Reading • SOA and API Convergence Strategy and Tactics • Promoting service reuse within your enterprise and maximizing SOA success • REST Easy: API Design, Evolution, and Connection • Enterprise Integration Patterns with WSO2 ESB • WSO2 Carbon: The Composable Platform Advantage
  30. 30. Thank You!

×