> This always seemed strange to me. If your team can't be trusted not to make spaghetti in a monolith, what stops them from making distributed spaghetti in microservices?
It's far harder to update multiple services to handle requests they should not handle, let alone update a deployment to allow those requests to happen.
Walls make great neighbors, just like multiple services make teams great at complying with an architecture constraint.
It's far harder to update multiple services to handle requests they should not handle, let alone update a deployment to allow those requests to happen.
Walls make great neighbors, just like multiple services make teams great at complying with an architecture constraint.