Patterns are the universal language of architects to communicate, refer, implement and improve. Architecture patterns from traditional SOA (service-oriented architecture) to ROA (resource-oriented architecture) and today to MSA (microservice architecture) drive most enterprise architectures today. Subpatterns such as EDA (event driven architecture) and WOA (web oriented architecture) also has a lot of traction today. These high-level concepts provide many best practices for enterprise architects that are looking to evolve their existing enterprise architecture or for those creating newer enterprise architecture strategies.
However, where should do we draw the line? Is SOA still the way to go or should we focus on MSA? During this session, Asanka will critically analyze the good, the bad and the ugly (if any) of the various architecture patterns, and jointly figure out where they should fit in.
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
operational expenditure.”
7. Enterprise architecture has changed today
- Less visibility to projects
- Difficult to find
- Availability
- Ownership
- (as a result EA provides *-platforms)
- 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)
- Integration/APIs is key (extend to connected business)
- Companies without integration are falling behind
- Heterogeneous systems
9. Evolution of architecture patterns
- Object oriented : OOP
- Component based : COM/DCOM/CORBA
- Open distributed processing : ODP
- Enterprise application integration : 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”
28. Microservice architecture (MSA) is a
pattern for building and delivering
service-oriented applications with two
primary objectives: agility of delivery
and flexibility of deployment.
Source : http://gartnercom
29. MSA is not based on all-new architectural
principles; it combines SOA best practices
with modern application delivery tooling
and organizational disciplines.
Source : http://gartnercom
31. A microservice must have a single
purpose and be loosely coupled in
design and deployed independently of
other microservices.
Source : http://gartnercom
35. Business architecture patterns
- Maturity of process systems (MOPS)
- Platform enabled agile solutions (PEAS)
- Submission interface (SI)
- Make your logic explicit (MILO)
- ….........