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.
AWS Lambda
111–120 of 164 posts
Re: AWS Lambda
#112Earlier quoted context omitted.
Really douche to use a computer science term as your product name, are they going to trade mark that or are the just happy with the confusion it will cause.
I have a hard time believing there is cause for confusion here, have Physicists been stumped by Amazon Redshift? I'm not being facetious, I just don't see how a product name that is niche to people using Amazon services is likely to confuse people. Also, CS hardly owns the greek letter lambda, it like many greek letters has been used for many products and features over the years. Delta is an airline, but they're doin…
Re: AWS Lambda
#113Re: AWS Lambda
#114Earlier quoted context omitted.
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.
To be fair, you have to pay per unit for these services, so as long as people are using them, Amazon is making money. Putting a service out to pasture in maintenance mode probably wouldn't cost that much.
Re: AWS Lambda
#115Earlier quoted context omitted.
It seems like you're limited to 25 concurrent lambda functions executing (at least at this time). This looks like it's more geared towards enabling you to automate / orchestrate your AWS resources, that run customer-facing code.
The 25 function limit is probably one of those small defaults that's easy to change, like the 20 instance limit.
Just like how you can get specific increases on your spot bids so long as you acknowledge that if you get a spot spike, and your personal limit is far greater than the spike -- you'll be charged your rate.
Re: AWS Lambda
#116Earlier quoted context omitted.
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
#117Earlier quoted context omitted.
I have a hard time believing there is cause for confusion here, have Physicists been stumped by Amazon Redshift? I'm not being facetious, I just don't see how a product name that is niche to people using Amazon services is likely to confuse people. Also, CS hardly owns the greek letter lambda, it like many greek letters has been used for many products and features over the years. Delta is an airline, but they're doin…
The meaning of "lambda" in computer science is functionally (no pun intended) similar enough to what amazon is selling that people learning programming and nontechnicals or even IT pros who work with programmers will inevitably be confused.
Naming the product something that closely resembles its functionality seems like a great idea for a product. It's still Amazon Lambda, and I think it's very unlikely that people will simply refer to it as "Lambda." If CS students find themselves hopelessly confused by this product name, they are going to have a real hard time tying their own shoes.
If you search for Y Combinator, luckily, https://en.wikipedia.org/wiki/Y_combinator still shows up on the first page of results, I expect the same will be true for Lambda, so I can confidently say we won't lose a generation of CS students to this faux pas.
Re: AWS Lambda
#118Sounds a bit like Mirage OS to me ( http://www.openmirage.org ).
Re: AWS Lambda
#119What 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).
Re: AWS Lambda
#120Earlier quoted context omitted.
Yes. From the bottom of TFA: Scheduled Tasks AWS Lambda functions can be triggered by external event timers, so functions can be run during regularly scheduled maintenance times or non-peak hours. For example, you can trigger an AWS Lambda function to perform nightly archive cleanups during non-busy hours.
That's great news. Thanks mate.