Microservice within a Monolith v1

Transcript

1. Microservices in a Monolith Not so much Microservices, more Event

   Driven Architecture

2. Joop Lammerts Developer @procurios for +3 years @jlammerts

3. Procurios Cluster

4. Procurios Cluster for context

5. Our Monolith

6. Our monolith ~ backend: 3.000.000 lines of code distributed over

   18.000 PHP files ~ frontend: 350.000 lines in 1800 JavaScript files 800.000 lines of CSS code

7. Usage

8. Usage • 2000 clients • 800.000 users • 500.000 visitors

   an hour
9. None

10. Microservices, or microservice architecture, is an approach to application development

    in which a large application is built as a suite of modular components or services. Assumption

11. Microservices, or microservice architecture, is an approach to application development

    in which a large application is built as a suite of modular components or services. Assumption

12. Modules

13. None
14. None
15. None

16. Modulair Monolith

17. Modulair Monolith • Bounded context with no dependencies on each

    other • Information can be duplicated for each bounded context

18. Modules sent messages

19. None
20. None
21. None

22. What to do with your legacy Monolith?

23. Take aways Locate and isolate Bounded contexts and turn them

    into modules Let the world know what changed an Event Driven plugin architecture

24. Joop Lammerts Website: www.procurios.com Twitter: @jlammerts