21–30 of 164 posts
Right now the only language/runtime supported is js/node, but they intend to include others. (figured people would want to know this, and you have to scroll a ways to find out, so)
The jokes ppl make are starting to get a bit more real: https://www.destroyallsoftware.com/talks/the-birth-and-death...
Seems like a much more interesting announcement than the container service. Can see the architectures of dozens of our systms collapsing down with this.
It's a bit amusing to note that they could have built Lambda on top of their own previous Elastic Beanstalk Docker offering instead, but chose to build ECS presumably for cost reasons (which everyone who has evaluated Elastic Beanstalk's Docker support will understand.)
I’ve had a chance to use the service for a couple of weeks. My quick summary review is that it’s a little tricky setting up the IAM roles and security groups, but once you have that going, it works great! I see a ton of potential here in transforming the way people use AWS. I also put together the Netflix use cases in the keynote so if you have any questions I’ll try to answer them!
What does this mean to application development? Is it something revolutionay?
IMO what's really going to be revolutionary is what we end up doing with it, but we're going to have to wait a bit to find that out :)
Claiming that your code is a 'lambda function' makes it sound sexy, but.. isn't it really just a procedure? Unless I'm missing something and there is some higher-ordered capability for composing AWS lambda functions together in a way that permits the platform to perform lambda reductions or optimize resource allocation...
I’ve had a chance to use the service for a couple of weeks. My quick summary review is that it’s a little tricky setting up the IAM roles and security groups, but once you have that going, it works great! I see a ton of potential here in transforming the way people use AWS. I also put together the Netflix use cases in the keynote so if you have any questions I’ll try to answer them!
Claiming that your code is a 'lambda function' makes it sound sexy, but.. isn't it really just a procedure? Unless I'm missing something and there is some higher-ordered capability for composing AWS lambda functions together in a way that permits the platform to perform lambda reductions or optimize resource allocation...
Having reductions and composition would be really cool, but from what I could glean from the demos each function is containerized. Stateless and idempotent like lambda functions, but right now chaining more than one together requires an intermediary event.
Right now the only language/runtime supported is js/node, but they intend to include others. (figured people would want to know this, and you have to scroll a ways to find out, so)