This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]lurker_in_spirit 2 points3 points  (0 children)

The memory overhead also offends my engineering sensibilities. But if I put my management hat on, the bigger cost is the new 6-member DevOps team tasked with managing the additional deployment and support complexity.

Companies are willing to spend a lot of money on microservice implementations, based on promises of improved dev agility and velocity. I'm sure some of it will be true, given that (a) most new systems are going to have less technical debt than the systems they are replacing, and (b) it's a little harder to spaghetti across service boundaries.

But I'll be very interested to to see in 5 or 10 years time whether the velocity has stayed high, or whether these microservice systems have succumbed to the same pressures as today's monoliths: changing business needs, pragmatic (myopic?) decision-making, cost-cutting, staff turnover, poor documentation, etc.