tech, ranty, microservices and "serverless"
Amazon: "The move from a distributed microservices architecture to a monolith application helped achieve higher scale, resilience, and reduce costs."
Oh look, they've finally acknowledged what some of us have been saying ever since *checks notes* Amazon started pushing the microservices/serverless hype on everybody
But nooooo, why would you ever listen to anyone who *isn't* a megacorporation, surely they can't be more competent than Amazon!
re: tech, ranty, microservices and "serverless"
By the way, what's up with all these blog posts and videos that essentially just repeat the Amazon blog post, without adding anything new?
re: tech, ranty, microservices and "serverless"
@joepie91 that just sounds like the ad-supported blog business. quick content. what's the quickest way? copy and reword what's already out there
re: tech, ranty, microservices and "serverless"
@joepie91 honestly the whole enterprise software development industry (including open-source) is filled with so much shit, and grifters and just transfer of money over frankly nothing... whether that be the software itself or ad-attention reading developers at huge companies circle jerking over some great practice their business is financially invested in... so much wasted human energy
like ignoring the software optimized for profit over efficiency and the extra energy consumption that induces, what about the wasted human energy just spent supporting this useless transfer of money that results in imperceivable gains. and often those gains are just faster operations of said useless money transfers!
there is good open source software ecosystems out there, but the good comes from passionate developers, not corporations. it would still be produced without the corporations, just maybe a little slower.
sorry now I'm ranting, I just hate enterprise software dev lmao
re: tech, ranty, microservices and "serverless"
@joepie91 Yeah… there’s a place for both. As with all these things you should pick an architecture that meets your business’ needs, not whatever is in vogue. Monoliths will get you very far.
re: tech, ranty, microservices and "serverless"
@ohno Part of the problem with microservices is that it's not actually a new concept; the idea of "separating out some stuff to scale it separately" has been around for a long time.
What "microservices" means, however, is "separate out *everything* by default, regardless of whether you have a reason for it". Which is why I'm comfortable concluding that unlike service separation, "microservices" are just a fundamentally bad idea; the ignorance to context is built directly into the concept :/
@joepie91 wtf, some sort of mega-microservices? Amazing, spectacular, truly revolutionary, etc
tech, ranty, microservices and "serverless"
@joepie91@social.pixie.town Agh I've been saying this forever. It's so goofy. We just migrated my team's app, which is a monolith event loop based server contained in a single docker container, from on-prem to EKS. Spinning up my app was trivial. Writing all the configs for RDS, load balancers, etc., took weeks, from a team that does this all regularly. Our other teams who embraced microservices are going to take a quarter or so to spin up, and their push safety strategy is such a mess because of all the interdependencies from what is actually one application but basically every API endpoint is its own app/container.
I'm old and feel ancient when I try to wrap my head around why this was more efficient and how you even begin to debug this. Microservices make sense if they're truly their own application, like an auth sidecar, but why are so many apps being split up if they can't run independently? Why is the glue all vendor lock? My coworkers apparently need to deploy to AWS for local development because it requires AWS-specific services as its messagebus.
Something seems like it's gotta pop at some point.
Ok this was incoherent but point is, I've been trying to understand how we got here and why.
re: tech, ranty, microservices and "serverless"
Who wants to bet that now that Amazon has said it, the dev community will suddenly be all over monoliths again, those same people who ridiculed us for recommending against microservices because we weren't Amazon saying it?