You're gonna be eating your words when AWS releases a serverless container offering. The benefits of containers are huge – can run anywhere (on my machine!) and fully packaged OS-level dependencies. Reproducibility is one of Lambda's downfalls 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.
- 8 more replies
New conversation -
-
-
I'm sure you would've said the same about ECS, but lo and behold they released EKS to let run you Kubernetes pods
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
It'd be the same business model as Lambda is right now