An AWS lambda function powers this Twitter account: https://twitter.com/actdigstream
Considering that the lambda function was pretty easy to write, free to run, and very portable: why would an Appengine app be better?
I built a webhook consumer from scratch with API gateway and Lambda in a day. It's not the cheapest, but I don't have to worry about provisioning servers or scaling it up. Overall I'm pretty happy with it.
Re:Writing Cloud Functions
by kevindeasis on Wednesday February 10, 2016 @01:41AM
(#11071111)
The shortest explanation would be:
These will allow you to automatically scale up or down easily. You don't have to maintain your server.
It has its advantages and disadvantages.
Together with SES i am using lambda to route inbound email to http endpoint.
[dead]
Re:Writing Cloud Functions
by jsprogrammer on Wednesday February 10, 2016 @01:36AM
(#11071096)
What would be the benefit for the mom over Lambda or another solution?
Re:Writing Cloud Functions
by jayzalowitz on Wednesday February 10, 2016 @01:40AM
(#11071107)
Nothing over other solutions but it is being built on more of an elastic system, so you are only paying for the time your mom is using. (It took all my strength not to phrase that another way)
I.E. when would you use this over a plain old simple appengine app