The best systems I've worked on have all been well architected monoliths. The code is ugly as fuck in some places but that's what tech debt is.
If you release a bug to prod in your monolith, it is exactly the same as a dependent microservice releasing the same and bringing the cluster down. You get a crash either way, and at least with a monolith you're not spreading your call-stack over the network; it's all in memory.
Re:Go + Services = One Goliath Project
by lonelappde on Saturday December 21, 2019 @09:05PM
(#21854663)
A micro service can have non critical dependencies.
It's almost religious. The reaction some people have when you suggest monoliths is completely baffling. It's apparently just "known" that it is the correct approach to all problems, so, y'know, it's embarrassing for you to have even suggested otherwise.