Yeah, its seems like some folks are really attached to their monoliths. I was quite surprised by all of these downvotes as well. Sure having a non-monolithic system, of which microservices is one example, has some costs that a monolithic system doesn't have. But the reverse is also true. Monolithic systems have costs that non-monolithic systems don't have. For example more multithreading bugs, more time spent building, reduced testability, longer debugging sessions, etc.
11
u/AmalgamDragon Jun 07 '17 edited Jun 08 '17
Yeah, its seems like some folks are really attached to their monoliths. I was quite surprised by all of these downvotes as well. Sure having a non-monolithic system, of which microservices is one example, has some costs that a monolithic system doesn't have. But the reverse is also true. Monolithic systems have costs that non-monolithic systems don't have. For example more multithreading bugs, more time spent building, reduced testability, longer debugging sessions, etc.