J'adore DHH, il a la même vision que moi sur l'overcomplification du monde du dev (pour le plaisir de faire comme les grands éditeurs qui ont des problématiques qui ne seront jamais les notres) :
<<I think microservices and the hype around it is probably one of the most damaging, uh, trends that has hit web development in the last 10 years. Um, I think very few things have done more damage to sort of the integrity and the productivity of software development teams.
Then the premature application of microservices. I am a stound, stout and proud supporter of the majestic monolith. This idea that you have a single application that a single person can fully grasp, comprehend, understand, deploy, operate, and then as far, far preferable to this idea of having a fleet of microservices, a building, a hundred different toolkits and languages that no one knows how to sort of operate and go on.
Microservices is a great example of an organizational tech pattern. It’s not actually a programming tech pattern. Microservices is what you do when you have teams so large that they essentially need dominion over their own domain. Right. They need to sort of control their own boundaries and so on. And when you have 50,000 programmers, yeah, it’s a completely reasonable pattern and it makes total sense trying to apply it.
While when you have two, five, 2050 programmers... Jesus, no, just no.
[...]
Even if I think that the single page application front end is a horrifically overuse pattern, far more so than than even microservices. And I think, so the crimes, against programming humanities that have been done in the service of single page applications are far worse than the ones that have been done in the service of microservices.
But then of course, as it is, lots of people combine the two. So it’s a fleet of microservices serving a single page application, and that’s just where it go. Like. Co plan, my head explodes with like, yeah, I would rather retire and fucking, I don’t know, make weaved baskets than deal with that shit.>>