Reply to post: Re: You don't need to know how 1,600 services work

How does Monzo keep 1,600 microservices spinning? Go, clean code, and a strong team

Bronek Kozicki Silver badge

Re: You don't need to know how 1,600 services work

As for the resources wasted, it really depends what they use for serdes and how much of it they do. The slide mentions RPC, so hopefully they are not wasting CPU time for number-to-text-to-number conversions. This is probably the biggest resource sink, when operating on floating-point numbers, in the architectures I know. As for the asynchronous communication over the network, if the volume is not excessively large you mostly pay in latency rather than other resources.

The nice side of a well designed microservice architecture is that you can tell which services are little used and, because each is relatively simple, you can also retire them and/or move functions elsewhere without much impact elsewhere.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon


Biting the hand that feeds IT © 1998–2020