turnoff.us (credits)
Maybe an unpopular opinion, but I think if you’re not sure if you need microservices, then you don’t need microservices. I’ve had to clean up too many overengineered systems to be convinced otherwise.
Microservices can be useful, but far too many companies take a poorly designed monolith and split it into poorly designed microservices.
Everywhere I’ve worked that did micro services it was kind of a pain. One of the places I’ve worked had a simple monolith backend and it was great.
It’s going to be a mess regardless. The monolith is just tangled at a different layer. The only way to avoid a tangled mess is to incentivize proper engineering, and everyone is incentivizing time to market and delivery of barely working features, which are the antithesis of proper engineering.
My current hell at work summarized in one image
Completely unrealistic. The monolith is not retiring, it’s just getting stuffed into a docker image and saying “Hello, fellow micro services!”, while achieving a fraction of the old uptime because you’re also trying to run Oracle or MSSQL on AWS using EBS as the underlying storage, and none of those components were designed for that use case.
Time to break out the classic:
May I tempt y’all with some midiservices? A midiservice is a service that, on average throughout its lifespan, has between 1 and 3 programmers maintaining it.
thought it would communicate via MIDI instead of REST
Hmm should I now install a MIDI switch in my home server rack 🤔
might as well add a couple rack synths too while you’re at it
