6 ms·

why would Google write a blog post about AWS lambda while they have cloud functions in beta?[1] why would i use google endpoint with AWS lambda instead of AWS A

by thawab 9y ago

why would Google write a blog post about AWS lambda while they have cloud functions in beta?[1] why would i use google endpoint with AWS lambda instead of AWS API gateway? Going "multi cloud" using AWS lambda with AWS API gateway and Google cloud functions with endpoints is a blog post I'm interested to read. [1]https://cloud.google.com/functions/ https://cloud.google.com/functions/

plandis 9y ago
Seems like marketing to get people comfortable w/ Lambda and who are not going to switch to at least partially use Google Cloud?
nothrabannosir 9y ago
I don't know about google cloud endpoints, but AWS gateway is an absolute nightmare. Configuration is awful and communicating errors from backend to client is a travesty. The lowest of the low hanging fruit to compete with AWS on. If GEP is remotely coherent it will be a clear win.
- sheeshkebab 9y ago
  Yeah, API gateway was written as some hack it seems (or maybe they used some third party ESB or a soa framework and slapped cloudfront on it). All the swagger extensions to configure it, these 200 status codes for 500 errors - its all barely usable. Just take your own rest backend and put cloudfront on it and it you'll have more functionality and as much or more scalability and security, for an "api".
- masuo 9y ago
  Were you using a Lambda integration? I found the following blog to be useful: https://aws.amazon.com/blogs/compute/error-handling-patterns-in-amazon-api-gateway-and-aws-lambda/ https://aws.amazon.com/blogs/compute/error-handling-patterns...
- shivakrish 9y ago
  API Gateway PM here - Sorry to hear that. Would love to understand more details around the trouble you are having with API configurations. Please do reach out to us on our forums (https://forums.aws.amazon.com/forum.jspa?forumID=199 https://forums.aws.amazon.com/forum.jspa?forumID=199) so we can assist further.
sitkack 9y ago
AWS Lambda is more mature. But this article is really aimed at folks on AWS who should at least be using Google's ML services.
redwood 9y ago
Because GCP has 2% of AWS market share and they want to break in

by thawab 9y ago

plandis 9y ago

Seems like marketing to get people comfortable w/ Lambda and who are not going to switch to at least partially use Google Cloud?

nothrabannosir 9y ago

I don't know about google cloud endpoints, but AWS gateway is an absolute nightmare. Configuration is awful and communicating errors from backend to client is a travesty. The lowest of the low hanging fruit to compete with AWS on. If GEP is remotely coherent it will be a clear win.

sheeshkebab 9y ago
Yeah, API gateway was written as some hack it seems (or maybe they used some third party ESB or a soa framework and slapped cloudfront on it). All the swagger extensions to configure it, these 200 status codes for 500 errors - its all barely usable. Just take your own rest backend and put cloudfront on it and it you'll have more functionality and as much or more scalability and security, for an "api".
masuo 9y ago
Were you using a Lambda integration? I found the following blog to be useful: https://aws.amazon.com/blogs/compute/error-handling-patterns-in-amazon-api-gateway-and-aws-lambda/ https://aws.amazon.com/blogs/compute/error-handling-patterns...
shivakrish 9y ago
API Gateway PM here - Sorry to hear that. Would love to understand more details around the trouble you are having with API configurations. Please do reach out to us on our forums (https://forums.aws.amazon.com/forum.jspa?forumID=199 https://forums.aws.amazon.com/forum.jspa?forumID=199) so we can assist further.

sitkack 9y ago

AWS Lambda is more mature. But this article is really aimed at folks on AWS who should at least be using Google's ML services.

redwood 9y ago

Because GCP has 2% of AWS market share and they want to break in