[ansmithz42]

A post like this pops up every few months arguing one way or the other. I have lived in absolute nightmare monolith systems with so much cyclic dependency that you couldn't move without breaking something. So monolith isn't the answer. I have also seen many instances where people have completely missed the underlying principles of microservices and have ended up with an equal nightmare. Neither is a hero or panacea, what matters is to understand what you are building and why and get the interfaces correct. Then understand the principles of different architectures before moving forward. If you fail on this, you get predictably a nightmare. There is plenty of nightmare code sitting on this planet everywhere we look. My recommendation isn't to vilify either architecture but to understand their strengths and weaknesses.

[antonvs]

I agree. What’s the answer to the question “monolith or microservice”? The answer is “architecture”.

[mattgreenrocks]

“Architecture” and “software design” are seen as antiquated, but discussing microservices and monorepos are somehow seen as relevant and important.