There are many ways to slice an apple. Sometimes it is a good idea to build something as microservices, but you just have taken the wrong approach, and therefo

There are many ways to slice an apple. Sometimes it is a good idea to build something as microservices, but you just have taken the wrong approach, and therefore it is a pain in the *. So slicing it a different way might still be a microservice architecture but feel much better. Recently I thought about setting up a Firefox Sync server. The first bumper was when I learnt that the sync server has a dependency on the accounts server... But the full-featured accounts server, in turn, consists of a bunch of services of its own [1]: - fxa-content-server - fxa-profile-server - fxa-auth-server - fxa-oauth-server - browserid-verifier - fxa-auth-db-mysql After seeing that I decided to tackle that project another day. For Mozilla that architecture might be perfect, but for most people who just want to run a separate server for <10 people, that architecture is just a burden. [1]: https://github.com/michielbdejong/fxa-self-hosting https://github.com/michielbdejong/fxa-self-hosting