News for hackers. Stuff that matters.
Re:Azure Functions vs. AWS Lambda – Scaling Face Off by lvh on Monday January 08, 2018 @06:53PM (#16102123)
My experience so far on Google Cloud has been just as bad. I want a simple app that ingests DMARC reports.

- Google Cloud Functions can't ingest e-mail. Also, JS lockin if you care about which platforms are supported.

- Google App Engine can only ingest e-mail in the Standard environment. OK, fine. But the standard environment regularly takes almost a full minute to load and boot my app, after which the request is killed for taking too long. Additionally, the sample code (!) for opening new Stackdriver contexts breaks with a totally inscrutable error message.

You can say "well, maybe your app sucks", but it's been running on AWS (SES + Lambda) for months and every aspect about it has been painless.

Re:Azure Functions vs. AWS Lambda – Scaling Face Off by mayank on Monday January 08, 2018 @09:29PM (#16103024)
Use Mailgun to trigger a POST to your Cloud Function on receiving an email. Bonus: all the parsing is done for you.
Re:Azure Functions vs. AWS Lambda – Scaling Face Off by teej on Monday January 08, 2018 @10:50PM (#16103453)
I don’t know how magic is in Cloud Functions, but I personally set up Mailgun postbacks in AWS and it was a huge pain in the ass to configure correctly. I’d love I know if google does something differently that would have been easier.
Re:Azure Functions vs. AWS Lambda – Scaling Face Off by lvh on Tuesday January 09, 2018 @01:13PM (#16108293)
But the parsing code already works fine, that’s not really the hard bit. Then I get all of the lock-in for questionable benefit and something that Just Works on AWS.