Menu
Back to Discussions

when do monolithic architectures start to hurt? i think it's when you have too many teams working on the same codebase. its hard to manage and deploy changes then.

Perizat Satybaldy
Perizat Satybaldy
·15413 views
Hey everyone, I've been pondering lately when it's really time to ditch a monolith. We've all seen projects start out fine, but then they just become this tangled mess, right? When does all that tight coupling and shared code actually start slowing things down, making deployments harder, or even messing with stability, to the point where you think, 'Okay, maybe microservices are worth the hassle'? Is it how big the team gets, how complicated the code is, what the business actually needs, or something else? I'd love to hear your stories and what you watch for. Cheers,
37 comments

Comments

Loading comments...