2 ms·
The assertion that monoliths are taboo is a bit odd; “monolith first” has been pragmatic best practice for years: https://martinfowler.com/bliki/MonolithFirst.h
by theptip 4y ago
The assertion that monoliths are taboo is a bit odd; “monolith first” has been pragmatic best practice for years: https://martinfowler.com/bliki/MonolithFirst.html https://martinfowler.com/bliki/MonolithFirst.html.
- ch4s3 4y agoI think this depends on who you listen to, but I'm a huge fan of the monolith and wouldn't break one up unless I has a specific tech need(eg some weird library), a performance issue unaddressable in the monolith, or big organizational people problem and in that order.
- mirekrusin 4y agoExactly, Sam Newman says the same thing in "Building Microservices" book. I don't know where people got this idea but I've noticed the less experienced, the more noise they make about it.
- tiberriver256 4y agoMajority of people I work with think that there are only two architectures. Monolith and microservices. Microservices is the good architecture. Monolith is the bad architecture. Such a sad trend :( but seems to be very prevalent