All these announcement are making me feel sorry for all the other players in the cloud game. The other guys don't even come close.
Though several of them run architectures on open technologies, which places them in a different situation entirely.
AWS Lambda
91–100 of 164 posts
Re: AWS Lambda
#92I wish they hadn't named the units of computation "Lambda functions". Cause, you know there's already something known as a "Lambda function" in computer science. But kudos for Amazon for furthering the datacenter-is-the-computer approach. It is simply the right thing to do.
I'm guessing they borrowed it from this : http://lambda-architecture.net/
The Forbes article said it is named after Star Wars space craft: http://www.forbes.com/sites/benkepes/2014/11/13/more-amazoni...
But I think it is simply named after the functional language feature. The core concept of this service is function.
Re: AWS Lambda
#93> You can use any third party library, even native ones. [1] I realize they are starting with node.js, but I wonder how this will work? It sounds like they plan to support arbitrary dependencies. Will you upload a Docker container with your necessary dependencies? They talk about milliseconds until your code is running, and containers may be (?) slower than that. Or am I hoping for too much. [1] http://aws.amazon.com…
It's definitely possible to do this if you're not set on containers.
We do it at http://wym.io/ by putting our runtime library in the environment that the code runs in and keeping the runtimes around, keeping the environment clean along the way.
We're working towards doing all that (and more than) Lambda does in a deploy-your-own fashion...
Re: AWS Lambda
#94Werner Vogels's blog about Lambda: http://www.allthingsdistributed.com/2014/11/aws-lambda.html
Re: AWS Lambda
#95I’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!
Do you know if you can respond to events from SWS or SQS?
Not directly, no. However, the documentation states that you can use CloudTrail to log the requests from SQS to S3, then have changes to S3 trigger the events that can get your Lambda function to respond.
It's a little convoluted, but that seems to be the way they're going for now.
Re: AWS Lambda
#96I’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?
No idea, for the time being the only supported language is JS. I'm trying to understand if I can run ruby applications by glancing here and there... Didn't had the time to look into it yet, but everyone seems very excited about it.
Re: AWS Lambda
#97I'm so torn - on one side this is a very neat thing that'll save a lot of boilerplate, and on the other it screams of vendor lock-in.
I won't be surprised if someone writes a generic lambda library which given a cloud provider generates relevant mappings/code. Will take care of some of the vendor lock-in concerns ?
I think this would be the solution. I guess lambda is basically IFTTT at scale with more configurable "T" portion.
Anyway, libcloud seems to be leading the way in this kind of standardization, so that's good news. There's also providers that have drop in AWS-compatible APIs for some services. Then there is stuff like apache mesos for creating that infrastructure, which is less relevant to smaller companies.
But I suspect that the last thing Amazon wants is to turn into a commodity, so it's in their interest to release as many differentiators with non-standard APIs as they can.
Re: AWS Lambda
#98I'm so torn - on one side this is a very neat thing that'll save a lot of boilerplate, and on the other it screams of vendor lock-in.
Well, yes. That's the thing about AWS. It's a very feature rich & sophisticated platform, which is hard to replicate elsewhere with the same harmony without spending a great deal of investment.
Re: AWS Lambda
#99Sounds a bit like Mirage OS to me (http://www.openmirage.org).
Re: AWS Lambda
#100I love that it uses Node.js to start, but does it support NPM?
Looks like yes: http://docs.aws.amazon.com/lambda/latest/dg/walkthrough-s3-e... Now, how to deal with node packages that require libraries not on the default amazon linux ami?
From that example it looks like it doesn't support NPM directly, instead you download the dependencies locally and include the node_modules directory in the zip file you upload. Interestingly the example makes use of ImageMagick, which I don't believe is in the default AMI.