Majestic Monoliths

In an era where microservices get all the attention, let's give monoliths some love ❤️

Transcript

1. Pierre Goudjo How do we organise our code?
2. Some patterns are just about the code itself
4. Some patterns are more about the organisation of the code
5. 💩 Monoliths
6. 🤘 Microservices
8. They must be on something, right?
11. of micro services Advantages • Each service has its team with its own timeline, sta ff and objectives • Improvement opportunities are parallelized • No endless merge con fl icts • Domains are cleanly segregated
12. Really, not being sarcastic here… This is a great pattern
14. Only if you are Google, Amazon, Net fl ix…
15. At a certain scale, there is no other way to coordinate e ff ort
16. Micro services architecture is an organizational pattern not really a so ft ware pattern
17. “#1 rule of distribute computing: Don’t distribute your computing!” Martin Fowler
18. of micro services Challenges • Coordination • Service discovery • Authentication • Monitoring • Compatibility
19. Enter the Majestic Monolith
21. It’s an integrated system that collapses as many unnecessary conceptual models as possible.
22. Focus on delivering 
 business value
24. Any activity becomes creative when the doer cares about doing it right, or better John Updike
25. We can do better!!!
27. Enforcing the domain boundaries segregation at code level The Majestic Modular Monolith
29. But…
30. There may well come a day when The Majestic Monolith needs a little help
31. Here come the Citadel and its Outposts
34. either for organizational, performance or implementation reasons. The citadel can of f load some divergent behavior to the outposts
35. Embrace them with pride and a salute Monoliths are not that bad…
36. • https://m.signalvnoise.com/the-majestic-monolith/ • https://m.signalvnoise.com/the-majestic-monolith-can-become-the-citadel/ • http://domainlanguage.com More on the subject
37. @pierregoudjo The End..?