Monolith to microservices?
- 1. From monolith to microservices? Software Engineer @tomasjurasek www.tomasjurasek.net Tomáš Jurásek
- 5. In general we’ve been doing microservices, but not well.
- 6. Monolith • One team – Conway‘s Law • One application and technology • Deploy as one unit • Difficult to scaling
- 7. Monolith is the new equivalent for a Legacy
- 9. Modular monolith • More teams • Modularity • Easy to refactoring into Microservices
- 11. Is your organization ready?
- 12. Microservices „…services are independently deployable and scalable, each service also provides a firm module boundary, even allowing for different services to be written in different programming languages. They can also be managed by different teams.“ https://martinfowler.com/articles/microservices.html
- 13. Microservices
- 16. Full-stack developer myth „I‘m sorry, but if you‘re not designing the computer chips and writing the website then I don‘t wanna hear from you“ Charity Majors, GraftConf 2016
- 17. How to start to migrate a module from a monolith
- 21. • Find your bounded contexts
- 22. • Find your bounded contexts • Create an abstraction layer
- 23. • Find your bounded contexts • Create an abstraction layer • Create a service – no refactoring just a copy
- 24. • Find your bounded contexts • Create an abstraction layer • Create a service – no refactoring just a copy
- 25. • Find your bounded contexts • Create an abstraction layer • Create a service – no refactoring just a copy • Separate the Database
- 26. • Find your bounded contexts • Create an abstraction layer • Create a service – no refactoring just a copy • Separate the Database • Now, you can do refactoring
- 31. Questions?