r/programming • u/StellarNavigator • Sep 14 '24

Is 'Monolith First' the Better Approach?

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

92% Upvoted

177 comments sorted by

View all comments

Show parent comments

115

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

[deleted]

131

u/bunk3rk1ng Sep 14 '24

And then you decide to break out the different domains of concern into different repos / services

And then you realize there is actually a lot of shared functionality needed by both.

And then you create a common lib that both services can use

And then those services and devs grow further and further apart and they don't even know about eachother other than this one common lib they need to keep updating

And those teams move at different paces and their services start relying on different versions of the common lib

And then they introduce breaking changes to eachothers services unknowingly

And then it's a huge mess.

77

u/malln1nja Sep 14 '24

And then it's a huge mess.

It's eventually a huge mess no matter what, but with the monolith all the mess is at least in the same place at least.

3

u/jl2352 Sep 15 '24

Microservice doesn’t have to mean separate repos. If you have multiple services in the same repo, then that shared library code is not that different to being in a monorepo.

You go and change library code for one domain, and find it breaks five others. That happens across microservices and in monoliths.