I am often tempted to engage container folk thought leading about #serverless. But slowly realizing I am not their target audience. It is other container people. They are trying to ensure their tribe they will still exist in the new world.
-
-
Explain the business reason to me?
It'd be the same business model as Lambda is right now -
"run my code" gives more room for AWS to build magic and proprietary value than "run my container". The higher level abstraction may be worse dev UX in the short term than a container but I bet they that gap will close.
-
Sure today there isn't much difference between "run my code" and "run my container", but by embracing code, AWS leaves open many more futures. Like maybe a nodejs specific lambda platform that doesn't run containers at all an uses VM sandboxing.
-
I've got one other practical reason. But I think it is not for public twitter.
-
A *lot* of customers say they love the built in language model and just want better library capabilities. That’s not the same as containers and many do no want some container format model they need to deal with
-
But like I’ve been saying, that’s just a tooling issue. They’d only need to “deal” with it in the same way they do zipfiles. You think most Java Lambda devs really know the structure of them?
-
So what does a “container” format offer up? What does it solve?
-
Reproducibility. You can look out there at all the blog posts with ppl explaining how to compile things for Lambda – I'm sure you've seen them. I mean – AWS Sam Local uses docker-lambda just to try to reproduce the env reliably!
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

I do realize they can be much more, but you just described so many containers.