Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda

Post by shivakrish » Tue, Apr 25, 2017, 6:19 PM UTC

nothrabannosir wrote: post #23

thawab wrote: post #16

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/

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.

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) so we can assist further.

Post by jankedeen » Tue, Apr 25, 2017, 9:59 PM UTC

MichaelBurge wrote: post #12

Seeing all those services hooked together gives me the willies. It sounds like a right PITA to debug, and chaining them together in serial for a single request multiplies the chance of an error even if each individual node is pretty stable. I guess it's okay for a demo though. They're probably not setting an example so much as trying to throw as many services together to show off the technique.

You know, architecturally, at application level no one wants to deal with this but devs orchestrate nightmarish dependencies for deploys and hit 'endpoints' with aplomb in service architectures with only a playbook or data blueprint to follow. What's the point of fighting this?

Let the kids play.

Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda

Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda