Remember when serverless was going to revolutionize everything? Well, LLMs just delivered the killing blow.
Here's the thing: In an AI-assisted co...
For further actions, you may consider blocking this person and/or reporting abuse
Nice satire,
Oh you mean it?
Replacing cynism with experience:
15-minute execution limits
Thats the point of one time calls
Cold starts that make your app feel broken
With GO below 50ms, snapstart for java
tecracer.com/blog/2023/07/custom-r...
Surprise $10,000 bills
With scaled instances it would be about the same, just limit concurrent execution - just like in scaling
Vendor lock-in so tight it hurts
There are ways around it if you code solid
Or use tecracer.com/blog/2025/06/the-arch...
Debugging that makes you question your career choices
With unit test and now debugging in running lambdas also no problem
docs.aws.amazon.com/toolkit-for-vs...
me "Add autoscaling to my Lambda"
llm : its build into the service, you do not need to do anything
docs.aws.amazon.com/lambda/latest/...
This must be a joke
What part?:D
Cloud platforms are much much more than just running Docker services.
I think the big take-away here is really "Run your 'serverless' service collections in Docker to simplify your life." Because what is an LLM in this context?
It's a glorified search agent. You're asking it to Google the answer for you.
The other thing here is to ask yourself "Do I really need to structure this in a 'serverless' way? Or is it cheaper to do it with more control and less limitations?"
So many things wrong here:
I understand that people tried to shove everything into AWS Lambda, which was a huge mistake, but that doesn't mean we should throw it all away. There are legitimate use-cases for serverless.
But I understand, this isn't a real article, it's your way to push sliplane, your own service based on docker. I'm sure once you add some serverless functionality you will start singing it's praises.
Given the quality of this piece, I wonder if it will help your company, or hurt it.
Dev.to is about more than getting a backlink or trying to make a buck. Be better!
I think serverless has its niche, but running things in Lambdas is not at all trivial
The way you formulated it might be a bit extreme (sure to provoke clicks and comments, lol) but that doesn't mean it's not true - I think it is ...
At some point I also jumped on the "serverless"/lambda bandwagon, but I stopped being a "believer" a while ago - for sure there are some good use cases, but it's no longer my "religion", and in most cases there are probably better ways, as you pointed out ...
It's as with many hypes and overhyped things - NoSQL, GraphQL, Blockchain, Serverless - all of those haven't been the revolution they were made out to be - useful in specific "niche" scenarios, but none of them truly going "mainstream" :)
If you’re hating on ANY tech because your reliance on LLMs to properly use them is making you upset, than the tech isn’t the problem — you’re just a bad developer! This is exactly what the industry is starting to catch up with and being careful with new hires.
Get opinionated due to LLM work is career suicide right now. For anyone reading this, do the opposite of what this person is saying.
Serverless is actually still very much alive and cost-saving if you actually know how & when to use it. This is the first time I saw a ridiculous rant like this one — but it makes sense considering the shameless plug.
LLMs thrive on open standards and universal tooling, exactly why we built haveto.com to run AI workloads directly on-chain using containers, not proprietary setups.
No cold starts. No vendor lock-in. No YAML puzzles.
Just real AI compute, fully transparent, and deployable like any standard container.
If you’re tired of fighting your stack instead of shipping features, you'll feel right at home here.
Let’s build smarter, not more complex.
To make AWS lambda (or Supabase edge function, or Netlify edge function or whatever) you just need to know how to write a handler. To use Docker you need to be a Linux expert just like with bare metal servers. Lambdas are for small teams, Docker is for teams with dedicated devops guy onboard I guess.
There's no relation to the rise of LLM's to the end of serverless. LLMs can easily create terraform and/or CDK scripts that deploy straight to AWS or any cloud provider for that matter. Abstractions exist and LLMs will learn on those abstractions. Docker is an abstraction in itself and so are tools to deploy to the cloud
Yeah, I thought this was a serious article and I'm not surprised to find out that a container management company co-founder penned this. Very disingenuous
Now that's a take ..
Couldn’t agree more. The learning curve and black-box nature of serverless has always been a developer trap. LLMs just exposed it for what it is.
I mean LLMs have and will continue to change how we think of the entire software cycle, but I think serverless will continue to have its niche.
Oh yeah 100% agree, serverless will also have its niche. Just won't be the way to build apps for the majority
Of course the co-founder of a company that wants to sell you docker hosting is complaining about alternatives
Of course