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

41–50 of 62 posts

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

#41

Post by optimuspaul »

nine_k wrote: post #40
jknz wrote: post #31

I am wondering if the future of multi-cloud lies in a third party entity managing real-time auctions for cloud services. 1. The developer sets up some requirements: number of instances, X amount of CPU power, Y amount of memory, Z amount of storage, B amount of bandwidth, or other characteristics. These requirements are sent to the third party. 2. Cloud vendors (the "bidders") receive the characteristics needed by th…

How about moving gigabytes of data that underlie the application? The egress cost is not that low. The access latency is utterly important. Raw computing power on small amounts of data has a limited applicability.

This is one of the main reasons I think being cloud agnostic is a fools errand.

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

#45

Post by paulddraper »

jknz wrote: post #31

I am wondering if the future of multi-cloud lies in a third party entity managing real-time auctions for cloud services. 1. The developer sets up some requirements: number of instances, X amount of CPU power, Y amount of memory, Z amount of storage, B amount of bandwidth, or other characteristics. These requirements are sent to the third party. 2. Cloud vendors (the "bidders") receive the characteristics needed by th…

Unlikely.

IaaS providers differentiate themselves on performance and price, but also reliability, networking details, auxillary services, tooling, API intelligibility, and support.

Cloud agnosticism sounds like a worthy goal but 9/10 it's the wrong move as it reduces you to the lowest common denominator.

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

#46

Post by coredog64 »

pasbesoin wrote: post #26
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.

Trans-cloud, as opposed to multi-cloud?

cis-cloud?

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

#47

Post by numbsafari »

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?

I think you're right: the headline on the article is bad/awkward in terms of how most people use multi-cloud. I get the impression that Google uses this term internally very differently. I also think you're right that they are leaving out the not insignificant detail about egress pricing.

In the context of this article, I think what they are pitching is the idea that, if you are already running services on AWS, you can still leverage some of the value-added service provided by GCP (e.g., their Vision API) by fronting them with Google Cloud Functions.

So, for example, let's say you built, and are running, an ecommerce platform on AWS. Now you'd like to leverage some of Google's Vision services to make "visual recommendations of related products". You already let customers upload product images via S3. Now you can have a Lambda function forward that image to a GCP CloudFunction, have it get processed by your visual recommender system, and spit back out a list of SKUs that have a visually similar image.

I think the goal is to convince companies that you don't have to put all your eggs in one basket in terms of capabilities, rather than convince them to have availability/capacity between multiple clouds (which how I think most people would interpret the headline).

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

#48

Post by discodave »

tyingq wrote: post #34

Why would you want the resulting uptime (u1 * u2) plus the added egress costs for cross cloud chatter? Cross cloud just seems like a bad idea all around. Edit: Maybe for a migration?

Imagine somebody that wants to get the features of EC2 and the features of BigQuery or some of Googles ML stuff.

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

#50

Post by hueving »

optimuspaul wrote: post #41
nine_k wrote: post #40

Earlier quoted context omitted.

How about moving gigabytes of data that underlie the application? The egress cost is not that low. The access latency is utterly important. Raw computing power on small amounts of data has a limited applicability.

This is one of the main reasons I think being cloud agnostic is a fools errand.

It's also a reason putting things on the cloud is a fools errand. If you can be held hostage by a provider, you made a business mistake by going there in the first place.
Post reply on HN