> I've always got the impression that micro-services are a bad idea most of the time, apart from sometimes where they're not. I'll argue that if you're buildin

> I've always got the impression that micro-services are a bad idea most of the time, apart from sometimes where they're not. I'll argue that if you're building something, you should probably build it as a monolith, with the exception of some well-defined services (like authentication & authorisation). Once you've got version 1 built, then you know enough about the problem that you're ready to consider breaking stuff off into microservices (this is why auth^2 make sense to break off from the get-go: they're pretty well-understood at this point, so we all should know how to handle them). Premature microservicement is the root of much evil. Trying to break things up into services before you actually understand the problem will only lead to tears & suffering.