Complexity — for the sake of it

Something is wrong when people just pile on complexity to a system simply because complexity makes one feel smart.

There’s no real reason to have a fleet of “micro services” that each only barely do one thing. Doubly so when there are shared libraries between those services that ensure that they can’t be independently deployed.

It’s just complexity.

Perhaps it’s born out of fear? Service A feels messy, so I’ll make another service. Of course now you have two services, and inevitably both will become messy. A fear of refactoring. An abstract fear of breaking something. Ignoring the problem will do nothing but perpetuate the issues.