News for hackers. Stuff that matters.

A comment on AWS Lambda: a few years of advancement and we are back to stored procedures. Parent comment

Re:AWS Lambda: a few years of advancement and we are back to... by Mizza on Monday April 04, 2016 @02:06PM (#11423948)
Another major piece of this puzzle that people overlook is AWS API Gateway, which provides a web gateway to Lambda. It's a newer product (and quite poorly PM'd, quite frankly), but it's an important part of the puzzle that no other cloud function provider has yet.
[ Parent | on HN ]
Re:AWS Lambda: a few years of advancement and we are back to... by djhworld on Monday April 04, 2016 @02:12PM (#11423995)
I've not used API Gateway, but I believe Microsoft support invoking their 'Azure Functions' style lambda service via HTTP calls

https://azure.microsoft.com/en-us/documentation/articles/fun...

[ Parent | on HN ]
Re:AWS Lambda: a few years of advancement and we are back to... by jasonlotito on Monday April 04, 2016 @02:21PM (#11424087)
You can do that with Lambda as well. The API Gateway is an abstraction in front of that giving you more control then connecting to Lambda directly.
[ Parent | on HN ]
Re:AWS Lambda: a few years of advancement and we are back to... by nivertech on Tuesday April 05, 2016 @07:18AM (#11429489)
I tried to build a serverless contact form by hooking up AWS Lambda function into S3 HTTP API event source and it's hard to configure and not working well. In any case it's not an alternative to HTTP Request triggers in Google Cloud Functions or Azure Functions.
[ Parent | on HN ]
Re:AWS Lambda: a few years of advancement and we are back to... by Mizza on Monday April 04, 2016 @02:16PM (#11424031)
For some reason I can't reply directly to your comment, but from that chart it looks like you can invoke a function, but not pass it any input, which makes it vastly less useful, and means that it can be used for serverless web frameworks.
[ Parent | on HN ]