Ask HN: How Big Is a Microservice?
One thing that always frustrates me in technical discussions is that the things we talk about are never defined upfront. You can't have a meaningful discussion of Kubernetes use if one person says it's bad without mentioning they work on a 5 person team, while someone else says it's good because they work in a 100 person org.
Likewise, people argue monoliths vs microservices, but one person's idea could be microservice = 10,000loc monolith = 100,000loc, while the other person's idea is microservice < 100,000 loc, monolith = 1,000,000 loc. People could be disagreeing vehemently, yet agree without knowing that 100,000 loc is a good sized service.
So what is your definition?
3 comments
[ 3.4 ms ] story [ 21.3 ms ] threadI've definitely seen systems where the general gist was a microservice per data type, without any consideration of how those data types and the overarching domain were organized. And it turned out pretty terrible -- UI calls that were very coherent from a domain perspective blowing up into a chain of 3 or 4 calls to other services to get all the required data.
In reality, there was a primary data type with a few different types of supporting data. So a single microservice serving that primary data type along with the supporting data would have been quite appropriate.