Tech has a tendency to take cosmetic details of a thing that works well, and turn it into a trend. This is then avocated for with the expectation it'll make other things work well.

There no doubt exist principles that help build good software. But many "best practices" are just cosmetic. This is mostly harmless if they go with well-understood (theoretically) orthogonal principles.

"Microservices" not only lacks strongly related principles, it can make matters worse.


The above post was from January, and in recent weeks several discussions took place on birdsite involving some big companies expressing (or finally making public) similar viewpoints.

My favourite one:

"For the record, at Uber, we're moving many of our microservices to what some call macroservices (or wells-sized services)."


Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!