Live data from Hacker News

Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda

cloudplatform.googleblog.com

21–30 of 62 posts

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

#21

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.

Ya the only way I could ever see this being maintainable is if it's declarative. It takes a tremendous amount of boilerplate and configuration to perform what comes down to a one liner in any functional language or a formula in any spreadsheet. I think I would be more interested in a transform that converts a series of goroutines to lambda functions or something.

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

#23
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.

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

#24
post #8

this doesn't solve the biggest problem with multi-cloud which is data egress though. Even if latency is acceptable you would get killed on data transfer for any significant amount of data. am I missing something?

Exactly. Even moving data between services in AWS or Azure can become costly if you aren't managing it properly. Moving that data to another cloud provider (images and video) would be a tough sell considering that both AWS and Azure have similar services already.

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

#25

A (potentially) better approach to going multi-cloud is to use a CD tool like Spinnaker (spinnaker.io), which Google and Microsoft both support - and Netflix supports the integrations to AWS. (full disclosure: my startup, Armory.io, builds enterprise features on top of Spinnaker)

You’re right, however this article is not talking about deployment tools. It's about setting up a serverless/lambda runtime pipeline between AWS and Google Cloud. As far as I know, Spinnaker does not do anything for your application runtime.

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

#26
post #10

This is not multi-cloud as it is commonly defined: Simultaneously handle workloads with multiple cloud vendors, to prevent lock-in to a single vendor. Rather, this is passing workloads between AWS and Google to leverage the advantages of each. A useful strategy, but the title is a bit misleading as it goes against the colloquial definition of multi-cloud.

Trans-cloud, as opposed to multi-cloud?

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

#27
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.

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".

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

#28
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/

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.

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

#29
post #8

this doesn't solve the biggest problem with multi-cloud which is data egress though. Even if latency is acceptable you would get killed on data transfer for any significant amount of data. am I missing something?

In my experience egress is not the biggest cost though, it's compute and storage. Are my workloads the outliers?

For most people not running a CDN or Netflix I would also expect to see CPU or Ram the bottleneck.
Post reply on HN