WSO2Con USA 2015: Pattern Driven Enterprise Architecture
0 likes307 views
The document discusses enterprise architecture and its evolution, emphasizing the importance of patterns in addressing recurring IT problems. It highlights the shift towards integration and the adoption of various architectural styles including service-oriented and microservice architectures to enhance delivery agility and deployment flexibility. The document also stresses the role of business architecture in shaping effective solutions and creating a pattern catalog for architecture.
WSO2Con USA 2015: Pattern Driven Enterprise Architecture
- 1. Pa#ern Driven Enterprise Architecture Asanka Abeysinghe Vice President, Solu=ons Architecture WSO2, Inc.
- 2. ”Pattern" is a generic solution for a common recurring problem.
- 3. Picture credit : h#p://flicker .com
- 5. Enterprise Architecture “Manage the complexity of the IT environment and applies principles and techniques to reduce the complexity, improve efficiencies, and reduce capital and opera=onal expenditure.”
- 7. Enterprise architecture has changed today - Less visibility to projects - Difficult to find - Availability - Ownership - (as a result EA provides *-‐plaXorms) - Change management - Development cycles: - From 18 to 6 months to 3 months
- 8. Enterprise architecture has changed today - Real standards - Technical (REST, SOAP, protobuf) - Business (ACORD, HL7, FIX, FAST) - Integra=on/APIs is key (extend to connected business) - Companies without integra=on are falling behind - Heterogeneous systems
- 9. Evolu=on of architecture pa#erns - Object oriented : OOP - Component based : COM/DCOM/CORBA - Open distributed processing : ODP - Enterprise applica=on integra=on : EAI - Service oriented : SOA - Event driven : EDA - Resource oriented : ROA - Web oriented : WOA - Microservice : MSA
- 10. SOA : “Architecture paradigm to build highly loosely coupled distributed systems”
- 11. SOA : “Nothing NEW, architecture style to fix broken architectures”
- 13. SOA
- 14. System of Systems Layered Enterprise Architecture
- 16. Event-‐driven Architecture Picture credit : h#p://nfl .com
- 19. Resource-‐Oriented Architecture Picture credit : h#p://flicker .com
- 22. Web-‐Oriented Architecture Picture credit : h#p://flicker .com
- 24. Connec=ng the pa#erns. SOA
- 25. Microservice Architecture Picture credit : h#p://flicker .com
- 26. Picture credit : h#p://pwc.com
- 27. Picture credit : h#p://pwc.com
- 28. Microservice architecture (MSA) is a pa#ern for building and delivering service-‐oriented applica=ons with two primary objec=ves: agility of delivery and flexibility of deployment. Source : h#p://gartnercom
- 29. MSA is not based on all-‐new architectural principles; it combines SOA best prac=ces with modern applica=on delivery tooling and organiza=onal disciplines. Source : h#p://gartnercom
- 30. "Micro" is a concept of scope rather than size.
- 31. A microservice must have a single purpose and be loosely coupled in design and deployed independently of other microservices. Source : h#p://gartnercom
- 32. MSA : reference architecture Picture credit : h#p://gartnercom
- 33. MSA : reference architecture
- 34. Requirements Current applica1ons/ systems Δ Delta Business architecture : business pa#erns
- 35. Business architecture pa#erns - Maturity of process systems (MOPS) - PlaXorm enabled agile solu=ons (PEAS) - Submission interface (SI) - Make your logic explicit (MILO) - ….........
- 36. Architecture approach Business Architecture Solu1on Architecture • Level 0 • Level 1 Applica1on Architecture • Integra1on • Datamodels • APIs Run1me Architecture • Capacity Planning • Deployment • Security Business architecture pa#erns Solu=on architecture pa#erns Applica=on architecture pa#erns Deployment architecture pa#erns
- 37. Create your own pa#erns and build a catalog.
- 39. Used it before Error proof Architect’s language Catalog PATTERNS
- 40. Thank You! @asankama h#p://asanka.abeysinghe.org asankaa AT WSO2.com