I thought the linked article about how Khan Academy eventually migrated to multiple services was a good example of when introducing micro services is a good idea:
They had already scaled the mono service about as far as it could go and had a good sense of what the service boundaries should be based on experience.
A very large code base full of loosely related functionality makes it more and more likely a change in one part will break another part in unexpected ways.
Django on Render( and presumably a heroku) just works.
It's still much more work that just dropping in a Firebase url. Firebase can lead to poor design choices and come back to bite you, but hopefully by then you've already raised a few VC rounds and you're rolling in dough.
You basically pay databricks a “fee” to choose the more appropriate and modern stack for you to build on, and keep it up to date. Never used it, but it handles with lots of the administrative bs (compliance, SLAs, idk) for you so you can just ship.
Damn they trained a model that so deeply embeds human experience it actually feels hunger, yet self aware enough it knows it’s not capable of actually eating!
https://blog.khanacademy.org/go-services-one-goliath-project...
They had already scaled the mono service about as far as it could go and had a good sense of what the service boundaries should be based on experience.
reply