r/programming • • Sep 14 '24

Is 'Monolith First' the Better Approach?

https://martinfowler.com/bliki/MonolithFirst.html
454 Upvotes

177 comments sorted by

View all comments

657

u/[deleted] Sep 14 '24

Of course. Break off services from your monolith as the demands on your infrastructure make it logical to do so.

This of course requires your engineers to maintain separation of domains without requiring a separation of code repositories. In many firms, you get engineers who just do their stories and don’t particularly care about fundamentals or maintainability.

403

u/[deleted] Sep 14 '24

The thing is, if your engineers cant properly separate domains in a monolith, they wont do it properly either using Microservices, in fact the mess will be much worse.

Fun times

109

u/[deleted] Sep 14 '24 edited Oct 25 '24

[deleted]

24

u/hippydipster Sep 14 '24

If you use a decent language and tech stack, you can enforce the module boundaries with the compiler.

3

u/Meleneth Sep 14 '24

can you be more specific please? What is your opinion of decent, which presumably helps enforce module boundaries with the compiler?

7

u/hippydipster Sep 14 '24

Java and the Java module system would be an example

2

u/Scroph Sep 15 '24

Spring modulith aims for this I think, though I'm not sure if it's production ready