Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Splitting the Monolith

91 views

Published on

Lighting talk. Tips and aspects to consider when breaking big systems into microservices.
TWReThink NY. May 2016

Published in: Software
  • Be the first to comment

  • Be the first to like this

Splitting the Monolith

  1. 1. SPLITTING THE MONOLITH Maria Gomez Tim Cochran
  2. 2. Loosely coupled Highly cohesive Single responsibility Microservices Loosely coupled Highly cohesive Single responsibility Monolith
  3. 3. Identify contexts
  4. 4. ACME e-store Payments Customer ServiceRecommendations
  5. 5. Decouple contexts
  6. 6. ACME e-store Payments Customer ServiceRecommendations
  7. 7. ACME e-store Payments Customer Service Recommendations
  8. 8. Choose the context to extract first
  9. 9. Payments Customer Service Recommendations ACME e-store ▫︎Pace of change ▫︎Performance ▫︎Security ▫︎Team structure ▫︎Dependencies (internal or external) ▫︎Technology How to decide:
  10. 10. Untangle dependencies
  11. 11. Payments Customer Service Recommendations DB
  12. 12. Payments Customer Service DB DBDB /payments/123 Recommendations
  13. 13. Payments Customer Service Reference Data Recommendations
  14. 14. Payments Customer Service Recommendations
  15. 15. Payments Customer Service Journal Recommendations /journals/123 /journals/456 /journals/789
  16. 16. ANTI PATTERNS ▫︎Start with small services ▫︎Big up-front design ▫︎Not letting your consumers define your API’s
  17. 17. Tim Cochran Maria Gomez THANKS

×