Every professional activity, we process information to do something-a doctor, a journalist, educator, lawyer, engineer, graphic designer, et cetera-will have a copilot, a personal AI within 2 to 5 years that will be amplifying of their abilities. Replacing method calls and module separations with network invocations and service partitioning within a single, coherent team and application is madness in almost all cases.So, look, I think one of the things that Satya Nadella and the whole crew at Microsoft is showing the kind of old Steve Jobs thing, which is no company can't be massively amplified and reinvented by kind of a new product, and what the whole crew there has done by recognizing and supporting the OpenAI mission but also then building the commercial products, and these products are just, you know, like transforming.
CLIPY ACCESSIBILITY CODE
Now you went from writing bad code to building bad infrastructure.īecause it drives a lot of new spend, it drives a lot of new hiring… So a lot of people get addicted to all the flourishment of money, and marketing, and it’s just a lot of buzz that people are attaching their assignment to, when honestly it’s not gonna necessarily solve their problem."īingo. "We’re gonna break up and somehow find the engineering discipline we never had in the first place. Kelsey Hightower, one of the leading voices behind Kubernetes, put it beautifully in 2020:
I wrote an ode to The Majestic Monolith way back in 2016. It's been eating brains since the dark days of J2EE (remote server beans, anyone?) through the WS-Deathstar nonsense, and now in the form of microservices and serverless.īut this third wave seems finally to have crested. Another strain of an intellectual contagion that just refuses to die. In many ways, microservices is a zombie architecture. An organizational pattern for dealing with intra-company communication at crazy scale when API calls beat scheduling coordination meetings.īut, as with many good ideas, this pattern turned toxic as soon as it was adopted outside its original context, and wrecked havoc once it got pushed into the internals of single-application architectures. The far more reasonable prior to microservices. What makes this story unique is that Amazon was the original poster child for service-oriented architectures. That really sums up so much of the microservices craze that was tearing through the tech industry for a while: IN THEORY. Now the real-world results of all this theory are finally in, and it's clear that in practice, microservices pose perhaps the biggest siren song for needlessly complicating your system. However, the way we used some components caused us to hit a hard scaling limit at around 5% of the expected load." In theory, this would allow us to scale each service component independently. Here's the telling bit: "We designed our initial solution as a distributed system using serverless components. What a win!īut beyond celebrating their good sense, I think there's a bigger point here that applies to our entire industry. This move saved them a staggering 90%(!!) on operating costs, and simplified the system too. The Prime Video team at Amazon has published a rather remarkable case study on their decision to dump their serverless, microservices architecture and replace it with a monolith instead.
0 kommentar(er)
