The slides from the Microservices Architecture (MSA) presentation made at The Open Group conference 2015, in San Diego, CA, USA. The co-chairs of the MSA project, Som B and Ovace M, presented and spoke on their current work and their findings from The Open Group project.

1. MicroservicesArchitecture (MSA)
The Open Group project
Somasundram Balakrushnan
Enterprise Architect,
Cognizant
Co-Chair - MSA (The Open Group)
Ovace A. Mamnoon
Enterprise Architect,
HP
Co-Chair - MSA (The Open Group)

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 our own and do not express the views or opinions of our current or past employers.

3. Introduction
• Who are we?
• What are we doing?
• And why?

4. Our Journey to MSA
•Genesis in early 2014…
•What is MSA?
•And why do we need it?

5. Picture this…
Unix way  cat opengroup.txt | sort –d | more

6. System/
Application-1
System/
Application-2
System/
Application-3
Server Side
component
Server Side
component
Server Side
component
Without MSA

7. Reality with MSA
External interfaces
API-1 API-2 .. .. .. API-N
System/
Application-1
System/
Application-2
System/
Application-3

8. MicroservicesArchitecture (MSA)
The Open Group – Project Charter

9. 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

10. Why Microservices…
It’s all about managing and reducing risk for business!

11. Considerations…
It’s about common sense and practicality

12. 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. ”

13. Outcomes…
Organization
Business
function
Business
Function
Business
Function
Business Unit

14. MicroservicesArchitecture (MSA)
Characteristics of

15. MSA: Characteristics
Survey
Survey Members:
• Participants from various
member companies
• Researched, Experienced,
Practitioners of MSA
• Leaders & Experts of EA and
SOA

16. Key Defining Characteristics
Single Responsibility
Self Containment
Service Independence
Highly Decoupled
Highly Resilient

17. Supporting Characteristics
Decentralized
Data
Management
Implementation
Agnostic
Scalability &
Stability through
Parallelism
Stable Contract
/ API
Point-to-Point
Integration
Federated /
Autonomous
Governance
Single Team
end to end
Ownership
Monitoring and
Instrumentation
Enabled

18. MicroservicesArchitecture (MSA)
Industry Trends & Observations

19. Building Blocks
Microservices
Framework
Platform (IaaS/PaaS)

20. Enabling Platform Components
• Monitoring & Automation (Service Delivery & Operations)
• Cloud deployment (IaaS/PaaS)
• Container Technology
• Service Discovery
• Light weight messaging
• API Gateways
Microservices
Framework
Platform (IaaS/PaaS)

21. Enabling Technology & Ecosystem
• Docker, Node.js
• Apache Mesos
• Apache ZooKeeper
• Swagger
• Consul
• HA Proxy
• Spring Boot, Akka ….

22. MSA Challenges
• Granularity & Decomposition factors
• Chattiness & Fan Outs
• Payload Serialization
• Testing Microservices
• Governance
• Dependency Management
• Service Versioning

23. Service Granularity
MonolithNano
Line of Granularity
More of an Art than Science
Consider Business flexibility
& agility needs
Beware of Monoliths and
Nano-Services

24. What Next?
 Whitepaper – Target: Summer 2015
 Enterprises can start piloting MSA
 Preparing the platform & framework