Re:How does Monzo keep 1,600 microservices spinning? Go, cle...
by okal on Monday March 30, 2020 @06:01AM
(#22726568)
I think a lot of people are extrapolating from their experience with monoliths and imagining that Monzo devs are maintaining 1600 tiny monoliths. That's an anxiety-inducing thought.
Re:How does Monzo keep 1,600 microservices spinning? Go, cle...
by Nextgrid on Monday March 30, 2020 @06:36AM
(#22726770)
I would prefer maintaining a "tiny monolith" over a micro service. At least with the monolith you're writing value-delivering business-logic code. From my experience with micro services you spend more time on boilerplate and the whole HTTP/RPC part and the communication with other services than the actual task the service is supposed to be doing.
Re:How does Monzo keep 1,600 microservices spinning? Go, cle...
by conjectures on Monday March 30, 2020 @08:37AM
(#22727504)
Or, maybe you are spending a bunch of time making sure you don't break a rats' nest of dependencies and waiting for things to build.
After the n^th iteration of building an rpc server, such things may be fairly standardised, no?
That sounds large but if you have 1600 microservices you are _most likely_ writing a single service where you'd normally write a class. Does 50 classes per engineer sound like a lot? Sure does but they didn't create this infrastructure out of thin air - this is an accumulation of many years. For sake of the arguments let's say 2 years. Across 24 months that's only 2 microservices per developer per month.
Not unthinkable, and this is assuming only 20% of their engineering force is actually productive.
[1]https://monzo.com/blog/2018/06/27/engineering-management-at-...