When does it make sense to just stick with a monolith, even if everyone's talking about microservices?
Xanti Larsson
·1122 views
I've noticed lots of teams just dive into microservices for new stuff, even when it's not a huge project. It's like everyone just assumes microservices are the way to go from the start now. But sometimes, you know, all that extra work managing separate services, deployments, and getting them to talk to each other just doesn't seem worth it for smaller or simpler apps. So when do you actually say, "Hey, a monolith makes more sense here, at least for the time being"? What kind of projects or team sizes make you lean towards a monolith instead of jumping straight to distributed?
4 comments