"a particularly structured zipfile"
I do realize they can be much more, but you just described so many containers.
-
-
-
Replying to @hichaelmart
twitter is hard. Maybe were not really disagreeing? I'm also trying to cram too many points into too few chars? 1. AWS has business reasons to avoid containers as a packaging format 2. containers are fine things, but increasingly irrelevant to serverless devs
1 reply 0 retweets 1 like -
Replying to @southpolesteve
Explain the business reason to me?
It'd be the same business model as Lambda is right now1 reply 0 retweets 0 likes -
Replying to @hichaelmart
"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.
2 replies 0 retweets 0 likes -
Replying to @southpolesteve @hichaelmart
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.
3 replies 0 retweets 1 like -
Replying to @southpolesteve
That's demonstrably false – the Go Runtime is a perfect example. It's *more* generic than the other runtimes – it just runs a binary you upload. That literally could be a docker binary – they'd just need to optimize some things (like they do with mounting /var/task etc)
1 reply 0 retweets 0 likes -
Replying to @hichaelmart @southpolesteve
The business lock-in for Lambda isn't the packaging or code structure – it's the fact that it integrates so well with all the AWS services, you just can't help but want to use it.
1 reply 1 retweet 5 likes -
Replying to @hichaelmart @southpolesteve
Well, that and the fact that it deploys so quickly and scales like the bejesus. And yeah, there'd be some challenges to get docker containers to cold boot as fast – would need to pre-mount (like it does currently with /var/task) for example. Maybe place some restrictions?
1 reply 0 retweets 0 likes -
Replying to @hichaelmart
I bet internally there are all kinds of strange reasons Lambda is built the way it is. I can only speculate. But I don't think the arch of the go runtime makes what I said obviously false.
2 replies 0 retweets 0 likes
I'd also guess a similar internal debate to what we are having happened. "long term business goals" vs "dev ux" vs "we needed Go support yesterday!"
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.