This presentation covers the evolution of micro services, patterns and challenges.

1. Micro Services Architecture
Rabbani Kaja Mohideen

2. Agenda
• Current problem
• What is micro services?
• Key Concepts
• Strengths & Weakness
• MS patterns
• Q & A

3. Products/Companies on MS

4. Monolithic Application

5. Layered Architecture

6. Layered Architecture – V1

7. Layered Architecture – V2

8. Layered Architecture – V3

9. Domain All Over

10. Monolithic – Issues…
• Coupling between tiers
• Service Spaghetti
• User exposed to Data model
• Adapt for changes
• Team productivity

11. Microservices
Agile
DevOp
s
CD MS
Speed to Market

12. Unix Pipes & Filters

13. Microservices
• Architectural style
• Fine-grained SOA
• Combine the best ideas of Agile software,
DevOps, and Reactive Systems
• Separate concerns

14. Separate concerns
• Inverse conway’s Law – teams own service groups
• Size doesn’t matter
• One developer independently produces a micro-
service
• Each micro-service is its own build & deploy
• Stateless business logic
• Stateful cached data access layer

15. Microservice Architecture

16. Key Challenges
• Integration
• Monitoring
• Testing

17. Integration Tips
• Standardize in the gaps between services, be flexible
about what happens inside them.
• Avoid RPC-mechanisms or shared serialization to
avoid coupling.
• Have one, two or maybe three ways of integrating,
not 20 ☺
• Avoid distributed transactions if possible
• Decentralized data store

18. Organize Around Business

19. Bounded Context
Boundary
Domain
Model

20. Scalability

21. Strengths
• Separation of concerns
• Loose coupling
SOA
Principles
• Distributed development
• Adapt to new Framework & languageAgility
• Independent deployment
• Efficient scaling
• Fault Isolation
Operational

22. Weakness
• Distributed transaction
• Dependency Management/API Versioning
• Expensive Remote Calls
SOA
Principles
• CommunicationAgility
• Operations overhead
• Fault Tolerance
• Deployment Complexity
Operational

23. Communication

24. Communication - Service Discovery

25. Monolithic to Micro services
• Start with New features
• Integration service
• Functional
Decomposition
• Code Duplication

26. Get together

27. Micro services?
• “Developing a single application as a suite of
small services, each running in its own process
and communicating with lightweight
mechanisms, often an HTTP resource API.
These services are built around business
capabilities and independently deployable by
fully automated deployment machinery”

28. Monolithic Vs Micro services

29. No to Micro Services
• Green Field Project
• Domain model is not clear
• Frequent change is not required

30. References
• http://microservices.io/
• http://www.infoq.com/microservices
• http://martinfowler.com/articles/microservic
es.html
• “Building Microservices” By Sam Newman