DEV Community

Discussion on: Building microservices, does size matter?

Collapse
jcmrva profile image
Josh M

I worked on a team that thought services should be split along the same lines that equivalent classes might be - the single responsibility advice taken to an extreme. The result: ~50% of the code in each service was boilerplate, intra-service issues were much far harder to debug, huge amounts of wasted time/effort/money, upstream SLAs were failing because of JSON serialization time, etc. That was when I learned the phrase distributed monolith.

In their defense, some of that came from leadership directives: "We'll definitely become the Amazon of ___, so..." (They didn't.)

Sometimes it's okay to mash things together.