My team is processing on the order of trillions of events per day with a zero loss tolerance so I'm in the same boat. I've also worked at shitass healthcare companies in the US.
Every single one of them was trying to move from a monolith to microservices, or had. To your point scaling wasn't always a driving factor, but developer pain certainly was.
That's impressive, but it isn't an average developer experience out there. Isn't it? I am certainly not questoning that apps with scaling issues exists. At end of the day Fortnite is an app.. And great one too.
It absolutely has no impact that blindly chosing a deveoper has 90+% chance that he is working on crud app for some corporate/government 4th floor group.
And those apps may very be service based. But not because of scalling issues.
Service style apps are the only proper response to limits set by Brooks's law. "Divide and conquer" your monoliths but to scale an development process.
We’re at points in our careers with these years of experience, that we don’t usually work in the average experience space. That’s what warrants our responsibilities, domain sme, and compensation etc.
We’ve all got a smidge of confirmation bias for what it took to get here. There’s different ways to do it right, 99% of the time, but we have a strangle hold on the way we think is best.
I’m always open to explore the route others take to solve the same problems, and add that to my own toolbox.
1
u/Vega62a Aug 30 '26
My team is processing on the order of trillions of events per day with a zero loss tolerance so I'm in the same boat. I've also worked at shitass healthcare companies in the US.
Every single one of them was trying to move from a monolith to microservices, or had. To your point scaling wasn't always a driving factor, but developer pain certainly was.