Monorails Application Design vs Cult of Microservices

RailsClub 2016 Talk

Transcript

1. Monorails Application Design vs Cult of Microservices Nikolay Bienko bikolya bikolyarb
2. Overview • Overview of Monolith vs Microservices • Why you should start with monolith • How to design monolith • How to split monolith 2
3. Pros of microservices • Maintainability • Granular scalability • Granular deploy • Reliability • Resilience • Separation of Concerns • Right tool for job • Management (small teams, fast delivery) 3
4. Problems with microservices • Technology hell • Deployment complexity • Latency between services • Network failures • Complex integration testing • Data consistency • Management (Conway’s law) 4
5. Prerequisites for microservices • Clear boundaries • Experienced team • DevOps (provisioning, simple deployment) • Monitoring • Logging • Design for failures • Appropriate teams structure 5
6. 6 Microservices architecture is not a goal. It’s (premature) optimization. The goal is successful business.
7. LMS Example 7
8. Monolith for the rescue • All successful companies started with monolith • Architectures are temporary • Evolutionary Design 8
9. Monolith First 9 "The only thing a Big Bang rewrite guarantees is a Big Bang!” – Martin Fowler http://martinfowler.com/bliki/MonolithFirst.html
10. Monolith: The Good Parts • Easier debugging (between call stack instead of socket) • No latency or network failures • Fast delivery • Easy deploy and provisioning • Less problems with monitoring • Separation of Concerns (when done right) • Good for small and medium teams • Good enough scaling (Stackoverflow, Shopify) 10
11. How to design monolith • Bounded Contexts • Domain Events • Event-Driven Architecture • Component-based Architecture • Failures handling 11
12. Bounded Contexts • Separation of Concerns • Loose Coupling • High Cohesion 12 http://martinfowler.com/bliki/BoundedContext.html
13. LMS Example Bounded Contexts: • LMS • GitLab • Notifications • ImportService • Calendar • Feed 13
14. LMS – Gitlab mapping 14
15. Qlean Example • Billing • Notifications Service • Accounting • Reporting • HR CRM • CRM • Recommendations • Pricing and Services management • Subscription management 15
16. Event-Driven Architecture 16
17. Event-Driven Architecture 17
18. Event-Driven Architecture 18
19. Event-Driven Architecture Explained 19
20. Event-Driven Architecture Explained 20
21. Event-Driven Architecture Explained 21
22. EventEmitter 22 https://github.com/bikolya/async_event_emitter
23. EventEmitter 23 https://github.com/bikolya/async_event_emitter
24. Event-Driven Architecture 24 https://github.com/bikolya/async_event_emitter
25. Event-Driven Architecture 25 https://github.com/bikolya/async_event_emitter
26. Event-Driven Architecture 26 https://github.com/bikolya/async_event_emitter
27. Event-Driven Architecture 27 https://github.com/bikolya/async_event_emitter
28. Atomicity 28
29. Layered Architecture 29
30. Layered Architecture 30
31. Component-based Architecture 31
32. How to split monolith 32
33. How to design monolith • Design internal bounded components • Clear interfaces between components • Pass only serializable objects between boundaries • Use Event-Driven approach • Improve infrastructure (logging, monitoring, provisioning) • Design for failures 33
34. Feedback is welcome 34 Nikolay Bienko bikolya bikolyarb