The document discusses strategies for splitting a monolithic architecture into microservices, emphasizing the importance of loosely coupled and highly cohesive service design. It outlines factors to consider when decoupling contexts, such as performance, security, team structure, and dependencies. The text also highlights common anti-patterns to avoid in the microservices extraction process.

1. SPLITTING THE
MONOLITH
Maria Gomez
Tim Cochran

3. Loosely coupled
Highly cohesive
Single responsibility
Microservices
Loosely coupled
Highly cohesive
Single responsibility
Monolith

4. Identify contexts

5. ACME e-store
Payments
Customer
ServiceRecommendations

6. Decouple contexts

7. ACME e-store
Payments
Customer
ServiceRecommendations

8. ACME e-store
Payments Customer
Service
Recommendations

10. Choose the context to extract first

11. Payments Customer
Service
Recommendations
ACME e-store
▫︎Pace of change
▫︎Performance
▫︎Security
▫︎Team structure
▫︎Dependencies (internal or external)
▫︎Technology
How to decide:

12. Untangle dependencies

13. Payments
Customer
Service
Recommendations
DB

14. Payments
Customer
Service
DB DBDB
/payments/123
Recommendations

15. Payments
Customer
Service
Reference Data
Recommendations

16. Payments
Customer
Service
Recommendations

17. Payments
Customer
Service
Journal
Recommendations
/journals/123
/journals/456
/journals/789

18. ANTI PATTERNS
▫︎Start with small services
▫︎Big up-front design
▫︎Not letting your consumers define your
API’s

19. Tim Cochran
Maria Gomez
THANKS