Re:How does Monzo keep 1,600 microservices spinning? Go, cle...
by x3al on Monday March 30, 2020 @05:30AM
(#22726415)
You can replace 'microservice' with 'class, but completely asynchronous and any interaction with it can fail without caller knowing if it succeed or failed at all'.
Re:How does Monzo keep 1,600 microservices spinning? Go, cle...
by imtringued on Monday March 30, 2020 @06:20AM
(#22726670)
Yes, that type of class is known as "actor".
Re:How does Monzo keep 1,600 microservices spinning? Go, cle...
by cfontes on Monday March 30, 2020 @06:31AM
(#22726731)
As someone with a little experience troubleshooting actor based systems, having 1600 of them sounds (actors not instances) like a nightmare.
Re:How does Monzo keep 1,600 microservices spinning? Go, cle...
by blackoil on Monday March 30, 2020 @08:04AM
(#22727307)
I have some experience with Akka. The amount of praying you have to do during production issues, no surprise it feels like a religion.
We tried it about 4 years back. Maybe there are some better debugging tools now, but for us both learning curve and prod issue pain did not make it worth it.
To me it looks like an Alan Kay style of OOP design. From that standpoint, replace 'microservice' with 'class' (or 'actor') and 1600 of them isn't that ridiculous.
It'd be an interesting system to browse. I'm actually curious if they've built any tooling around making the codebase easier to navigate and edit. Smalltalk handles a huge amount of tiny classes by having good browsing tools. What would you use for a Go codebase of this size?