This document summarizes Service Oriented Architecture (SOA) and how it can help address challenges in Enterprise Architecture (EA). It discusses how SOA enables loosely coupled distributed systems through independent services. Common SOA patterns are presented, including API-centric architectures. EA challenges like lack of visibility, integration issues, and fast development cycles are outlined. The document proposes addressing these through a reference architecture with layered (L0-L1) components and a configuration-driven Business Services Platform. It concludes by demonstrating thin-slice development capabilities enabled by SOA principles.

1. Establishing an SOA Focused
Enterprise Architecture
Asanka Abeysinghe
WSO2, Inc
Vice President, Solutions Architecture

2. Goal of the day
-
Service Oriented Architecture
Enterprise Architecture
EA challenges
How SOA helps to address EA challenges
Common business architecture pattern
Lab exercise (Solution building)
Q&A

3. Service Oriented Architecture
“Architecture paradigm to build highly loosely coupled
distributed systems”

4. Service Oriented Architecture cont.
“Nothing NEW, architecture style to fix the broken
architectures”

5. Pre-services Era

6. SOA at Kindergarten

7. SOA cont.

8. SOA today – Design Time

9. SOA today – Run Time

10. API-centric SOA
“API Management, the missing link for SOA success.”
- Sanjiva Weerawarana

11. API-centric SOA cont.

12. API Façade

13. Enterprise Architecture
“Manage the complexity of the IT environment and
applies principles and techniques to reduce the complexity,
improve efficiencies, and reduce capital and operational
expenditure.”

14. EA Challenges
- Enterprise Architecture has changed
- Less visibility to projects
- Difficult to find
- Availability
- Ownership
- Development cycles:
- From 18 to 6 months to 3 months
- Change management
- Real standards
- Technical (REST, SOAP, protobuf)
- Business (ACORD, HL7, FIX, FAST)
- Integration is key (extend to connected business)
- Companies without integration are falling behind
- Heterogeneous systems

15. The finale
YOU’RE
FIRED!
and
MEET MY
LAWYER!

16. Building the Reference Architecture
Solution

17. L0 (Level 0) – Architecture

18. L1 (Level 1) – Architecture

19. Example : MDM – L0

20. Example : MDM-L1

21. Business Services Platform : Component
Architecture

22. BSP : Magnitude View

23. BSP : Layered Architecture
Integration Layer - 1
Datamodel
Integration Layer - 2
Services Platform
Business Services
Datamodel
Data Layer

24. BSP – Implementation : Integration and Data

25. BSP – Implementation : Services and
Governance

26. BSP – Implementation : Business Processes,
Security

27. BSP – Implementation : Monitoring and
Portals

28. Code vs Configuration
“Professional coders make 100-150 errors per thousand
lines of code .”

29. Configuration Driven

30. Recap
SOA principles
EA challenges
Loosely coupled services
Loosely coupled development efforts (e.g.
accommodate some schedule asynchrony)
Flexibility under changing business
conditions
Flexibility under changing requirements
Fast time to market of new business
capabilities
Short release cycle with incremental utility
Heterogeneous environments
Choose the best tool for each job
Good governance practices and tools
Community-centric tools:
• Versioned repository
• Peer visibility and review
• Rich communication channels
• Issue and status tracking
• Automated build/test

31. Skip the Ad in N seconds ->|

32. Thin slice - Demo
- Configuration driven
- Pattern driven
- Decoupled architecture

33. Thank You
@asankama
http://asanka.abeysinghe.org
http://wso2.com