Or why the microservice cargo cult which has been going on for a while now infuriates me. It totally ignores the complexity it brings.

Interesting piece... why talking about microservices generally leads nowhere. This is a too loosely defined term and we're often confusing means and ends.

I'm not a huge fan microservice based architectures. That said the parallel done there is interesting and a good reminder that the "write programs that do one thing and do it well" quote is incomplete.

I'm obviously not in love with the complexity this type of architecture brings. That being said, this thesis brings an interesting approach to better detect failure scenarios in such systems.

Since this particular fad apparently doesn't want to die... this is a good reminder about why you want to do something simpler.

Looks like the morbid fascination for microservices is fading. This is very welcome. This piece is a good criticism of this particular fad and gives an interesting theory of why it came to be.

Even the giants are slowly moving back from microservices. DHH has a very cruel way to point it out, still that's true. Let's hope people realize the mistake it was in term of complexity.

Interesting explanations of the main drawbacks of microservices. Nothing is magical so you need to know what you loose, in this case this is mostly about increased coordination efforts and latency in feature availability.

Excellent piece, looking back to history to justify why microservices are mostly a fad. Check what your needs really are and depending on them pick the right way to decompose the problem or organize your teams.

The current microservices obsession not only invite undue complexity in systems, it also bring unprepared developers into network related traps. This is a nice summary of the common misconceptions around this.

Good arguments around the microservices hype. People advocate for it way more than reasonable, this applies only in rare contexts.

And that's why I find hard to swallow that "microservices" is the go to answer from lots of people nowadays when you discuss architecture. There are interesting promises on paper but that requires you to ignore several layers of complexity. It's likely fine to get there at some point, but bake in all that complexity from the start? I don't think so.

Stay away from the hype and introduce complexity in your systems only if it's warranted by the problem space you have to tackle. Most organizations don't need microservices, use them responsibly.