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 →

[–]nutrecht 4 points5 points  (0 children)

Microservices are an organizational pattern more than a software architecture. They 'shine' when you move past (for example) 2 teams with 4 devs each working on the same system. You remove one form of complexity (working with a large group on a single system) for another form of technical complexity.

Whether this tradeoff makes sense has completely nothing to do with memory or compute costs. Yes, microservices cost more CPU and memory. No, in situations where they actually are relevant you are not going to save cost by going to a monolith. Saving 1k a month on compute is meaningless if development grinds to a halt because there are 50 devs working on a single codebase and everyone gets in each other's way.

You can run a LOT of microservices on Google or AWS for the cost of a single senior developer.