Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Lambda

aws.amazon.com

Post reply on HN
Print view View original

61–70 of 164 posts

Re: AWS Lambda

#61

Post by Corrado »

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.

I'm guessing that this Lambda functionality is built on the new ECS (EC2 Container Service) which is built on Docker. Therefor, it should be reasonably doable to recreate it on-premises and escape the AWS lock-in. "should" being the operative word there. :)

Re: AWS Lambda

#62

Post by impostervt »

adelevie wrote: post #36

Is this comparable to IronWorker?

You can also configure your IronWorker more so than you can a lambda. For instance, I have an IronWorker that requires a library not installed by default, so I use the "deb" command to install it during the build process.

And of course, it supports more than just Node.js.

Re: AWS Lambda

#63

Post by Corrado »

joshuahutt wrote: post #13
jedberg wrote: post #3

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!

One thing I am struggling to understand is how much of my applications can be replaced with Lambda. I think it would be really awesome to make applications that do not have any dedicated instances associated with them, but are entirely based on the various AWS platforms. For some things, it seems like Lambda could be a drop-in replacement, whereas others, it would not quite fit the bill. Do you think it will be possi…

I recently had to set up a system to generate thumbnails from images uploaded into S3; precisely the example they give. This would be a godsend and replace a lot of complicated queues and ruby processes running on an army of EC2 instances.

Oh what I would have given to have this capability a year ago. :)

Re: AWS Lambda

#64

Post by dk8996 »

Is it me or AWS is releasing too many services... there is a service for everything. I wounder if they are just throwing stuff out there see what sticks... kinda like landing pages.

Re: AWS Lambda

#65

Post by apetresc »

erichmond wrote: post #47
spitfire wrote: post #34

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.

I'm guessing they borrowed it from this : http://lambda-architecture.net/

I'm not sure what Nathan Marz's "Lambda Architecture" has anything to do with AWS Lambda, though

Re: AWS Lambda

#66

Post by eva1984 »

notastartup wrote: post #60
MBlume wrote: post #4

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)

I saw it and was shocked that Python is not yet supported.

I guess it is due to the sanboxing issue, which is pretty hard to get right.

Re: AWS Lambda

#67

Post by poxrud »

dk8996 wrote: post #64

Is it me or AWS is releasing too many services... there is a service for everything. I wounder if they are just throwing stuff out there see what sticks... kinda like landing pages.

To be fair, unlike google they are not cancelling any services. I think Amazon first builds these services for internal use, and then releases them to the public.

Re: AWS Lambda

#69

Post by logicallee »

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.

No it doesn't, this is ridiculous. "On the one hand it's free cash; on the other hand we could end up liking the guy giving it to us."

Re: AWS Lambda

#70

Post by notastartup »

What about dependencies. What if you need a specific environment setup first in order to process. Would you end up paying 1 minute for each request just so that it can start installing bunch of stuff? Is it possible to just setup a VM of some sort and use that environment each time?

If thats possible Lambda would be like PiCloud but without Python, and will stick around (hopefully).

Post reply on HN