4 ms·
There were a number of red flags indicating that microservices were not a good fit here: > Microservices had been sold to us [...] It seems no one really unde
by karmakaze 7y ago
There were a number of red flags indicating that microservices were not a good fit here:
> Microservices had been sold to us [...]
It seems no one really understood the benefits or costs--somewhat understandable as there's no learning better than doing.
> Building on top of a third-party impacted how we could divide our domain into microservices.
Usually the features come together at the top where the user is, in this case it may be both the top and bottom.
> We couldn’t identify any obvious candidates in our monolith to be broken out into a microservice. So instead, we started drawing arbitrary lines between our domain models
This is how most first-time microservices designs fail drawing boundaries around 'nouns'. With each being a source of truth for information needed in many contexts. A microservice should be one of these contexts and the data it needs from each 'noun' source separately from serving requests.
> We have approximately 12 developers spread across 2 feature teams
This is the biggest red flag. The primary advantage of microservices is for scaling teams so each can deliver independently. With only 2 pizza-sized teams there's not much point.
There may still have been a useful feature that could be extracted into a microservice if given more consideration. Think along the lines of 'what has to change a lot for a particular recurring reason' might point somewhere. Another way is if there's a mixture in the tech stack, e.g. search is often split off.