Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda

cloudplatform.googleblog.com

Post reply on HN
Print view View original

11–20 of 62 posts

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

#11

Post by zeroxfe »

luhn wrote: 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.

> the colloquial definition of multi-cloud.

I know you can use multi-cloud to prevent lock in, but I've never heard the term used to strictly mean that. Almost everyone I work with uses the term multi-cloud as "workloads on multiple cloud vendors."

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

#12

Post by MichaelBurge »

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.

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

#13

Post by al_james »

doppenhe wrote: 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?

No exactly right.

As Google seem to be getting more serious about attracting aws converts and dual cloud deployments (eg in built aws vpc peering) I wonder if they will offer some kind of cut price data transfer to aws networks. That would be an interesting move.

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

#14

Post by ben_jones »

zeroxfe wrote: post #11
luhn wrote: 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.

> the colloquial definition of multi-cloud. I know you can use multi-cloud to prevent lock in, but I've never heard the term used to strictly mean that. Almost everyone I work with uses the term multi-cloud as "workloads on multiple cloud vendors."

My take is that "multi-cloud" means if one cloud goes down you don't have a service disruption. Or at least not a major one.

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

#15

Post by dmourati »

ben_jones wrote: post #14
zeroxfe wrote: post #11

Earlier quoted context omitted.

> the colloquial definition of multi-cloud. I know you can use multi-cloud to prevent lock in, but I've never heard the term used to strictly mean that. Almost everyone I work with uses the term multi-cloud as "workloads on multiple cloud vendors."

My take is that "multi-cloud" means if one cloud goes down you don't have a service disruption. Or at least not a major one.

RAID 1 vs RAID 0

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

#16

Post by thawab »

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/

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

#17

Post by plandis »

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/

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

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

#18

Post by techcofounder »

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)

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

#19

Post by datums »

luhn wrote: 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.

+1 Multi Cloud , has meant aws || azure || gce || vmware

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

#20

Post by tlarkworthy »

doppenhe wrote: 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?
Post reply on HN