AWS Lambda • Hacker News Board

Re: AWS Lambda

#31

Post by salimmadjd » Thu, Nov 13, 2014, 7:06 PM UTC

Amazon Echo (voice interface of IoT) + Amazon Lambda (the cloud services of (IoT) = Amazon disrupting home appliance IoT products.

Re: AWS Lambda

#32

Post by ncallaway » Thu, Nov 13, 2014, 7:15 PM UTC

cperciva wrote: post #14

Something I want: AWS Lambda code which responds to S3 PUTs by issuing Cloudfront invalidations. Anyone want to write this?

I imagine it would be very with the S3 Event Notification stuff they also released today: http://aws.amazon.com/blogs/aws/s3-event-notification/

Re: AWS Lambda

#33

Post by cperciva » Thu, Nov 13, 2014, 7:18 PM UTC

ncallaway wrote: post #32

cperciva wrote: post #14

Something I want: AWS Lambda code which responds to S3 PUTs by issuing Cloudfront invalidations. Anyone want to write this?

I imagine it would be very with the S3 Event Notification stuff they also released today: http://aws.amazon.com/blogs/aws/s3-event-notification/

Yes, exactly. Someone needs to write the code, that's all; I'll do it myself if necessary, but if someone else gets there first all the better.

Re: AWS Lambda

#34

Post by spitfire » Thu, Nov 13, 2014, 7:22 PM UTC

I 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.

Re: AWS Lambda

#35

Post by cschmidt » Thu, Nov 13, 2014, 7:24 PM UTC

> 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/lambda/details/

Re: AWS Lambda

#36

Post by adelevie » Thu, Nov 13, 2014, 7:25 PM UTC

Is this comparable to IronWorker?

Re: AWS Lambda

#37

Post by sync » Thu, Nov 13, 2014, 7:30 PM UTC

adelevie wrote: post #36

Is this comparable to IronWorker?

Yes, seems like a direct competitor to IronWorker to me.

IronWorker has a few benefits such as being able to run any docker container and react to a HTTP Post (webhook) directly, but overall very similar to Lambda.

Re: AWS Lambda

#38

Post by makmanalp » Thu, Nov 13, 2014, 7:30 PM UTC

I'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.

Re: AWS Lambda

#39

Post by orange_sharpie » Thu, Nov 13, 2014, 7:35 PM UTC

makmanalp wrote: post #38

I'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.

that's a REALLY good point! this feature seems really solid, but they seem to be putting a sort-of "golden handcuff" on you. If you have a distributed system on AWS which implements "lambda functions," you can forget about switching to Azure, or your own bare metal servers without having to go through some pain. "vendor lock-in" definitely seems to have been their motto here, very clever & great observation!

Re: AWS Lambda

#40

Post by marknadal » Thu, Nov 13, 2014, 7:36 PM UTC

Holy mind blowing awesomeness, this changes everything, yet I feel like this was such an obvious thing to do. So obvious that I can't believe it is real. This, ladies and gentlemen, is why AWS defines the cloud, they are so far beyond everyone else and still innovating, even and the most basic level.