2. Topics
• Introduction
• MSA Project Charter
• What is Microservices Architecture (MSA)?
• Key Defining Characteristics
• Supporting Characteristics
• Industry Observations
• Next steps
Disclaimer: Opinions expressed are solely my own and do not express the views or opinions of my current or past employers.
4. Our Journey to MSA
•Genesis in early 2014…
•What is MSA?
•And why do we need it?
5. Industry traction for Microservices Architecture…
Google Trends Blurbs from various sources…
By 2017, over 20% of large organizations will deploy self- contained
microservices to increase agility and scalability. – Gartner 2015 predictions
11. MSA Project Charter
• What is Microservices Architecture?
• Key Defining Characteristics
• Related / Supporting Characteristics
• SOA and Microservices Architecture
• Compare and Contrast SOA & MSA architecture styles
• Governance Impacts
• API & MSA
• Cloud & MSA
• Implementation Considerations for Microservices Architecture
• Skills / Competency needed
• Organization maturity
• Infrastructure support
12. Common Case for MSA
• Enabling Business Agility & Flexibility
• FasterTime-to-Market (via automated
infrastructure/deployments)
• Greater availability, stability and scalability…
• Partition the system…
• Federated team & DevOps..
• No Development Language Lock-in (Polyglot)
13. Considerations…
• The granularity question…
• Service proliferation
• maintainability' and 'cost‘…
• Technology flexibility…
• Team end-to-end Ownership…
• Security, Identity, Access…
14. Teaming Concepts
Conway’s Law:
“Any organization that designs a system (defined more
broadly here than just information systems) will inevitably
produce a design whose structure is a copy of the
organization's communication structure. ”
15. Outcomes…
• Streamline and agile software Life cycle…
• Teams organized around business domains…
• Ownership and empowerment (DevOp)…
• Scale only where needed...
• Continuous Deployment…
• Reduced CapEx & OpEx
Organization
Business
function
Business
Function
Business
Function
Business Unit
20. SOA vs. MSA – Industry Perspective
• MSA is SOA done right!
• SOA is dead, long live MSA!
• MSA = SOA + Dev Ops!
• SOA means different things to different people
….
21. SOA vs. MSA – Emerging PoV @ TOG
• MSA is an extension (or) a variation of SOA
• MSA is completely distinct and different than SOA
architectural style
• MSA is a sub-set of SOA (with overlapping
characteristics)
• MSA replaces SOA ("MSA is SOA done right")
28. Service Granularity
MonolithNano
Line of Granularity
More of an Art than Science
Consider Business flexibility
& agility needs
Beware of Monoliths and
Nano-Services
29. What Next?
Enterprises can start piloting MSA
Preparing the platform & framework
Enable faster time to develop services
Containerization & cloud considerations
Automation of deployment & auto-scaling
TOG: MSA_Whitepaper – Target: Summer 2015
Notes de l'éditeur
Som -
(Less than a minute)
Som – Story (MSA in context) – about a minute
Ovace – Story (MSA in context) – about a minute
Som to start with – 1 min
Ovace to continue – 30 sec
Open Groups story
Ovace – 1-2 minute
Ovace to Som – less than a minute
Som – about a 1-2 minute
One of the application/system could be COTS
Milestone – check should be here in (about 7-10 minutes)
Som – 1-2 minutes
Ovace – 2 minutes
Complexity: Functional bloat, governance, large teams, hand off issues…
13
Ovace – about 30 secs.
Reference: http://www.melconway.com/research/committees.html
Ovace – about a minute less than 2
Checkpoint – (8 to 10 mins.) => should be < 20 mins. overall.
Som – 1-2 mins.
(Talk about the process involved; themes…)
Survey-Member Companies: HP, Cognizant, IBM, ApjonTech, Coexiam Solutions, Raytheon Company
(Other Companies in Team): Capgemini, AT&T, American Express, TCS, Oracle, Nationwide
Som- 2-3 minutes
Talk on each char --
(The combination of the char, and the way they are realized sets MSA distinct..)
Som / Ovace – about a minute to 2
Top – ovace – 1 minute
Bottom ones – Som – 1 minute
Som / Ovace – about a minute to 2
Top – ovace – 1 minute
Bottom ones – Som – 1 minute
Som / Ovace – about a minute to 2
Top – ovace – 1 minute
Bottom ones – Som – 1 minute
Checkpoint – (7-10 mins) => About 30 mins.
Som- About a minute (max)
Talk about Frameworks / Libraries, and Platform.
Som – about 1-2 mins.
Som – about 1-2 mins.
Som – less than minute
Som – 1-2 mins.
Emerging challenges often associated with Microservices, as observed in the industry
Decomposition factors (how granular is a microservice?)