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

31–40 of 62 posts

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

#31

Post by jknz »

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 the developer. Each of them bid by providing a price per hour for the given characteristics.

3. The bidder with the lowest price wins the auction, sends back credentials to start deployment

4. The developer can start the deploy with the infrastructure provided by the lowest bidder!

All this may happen in less than one second, similarly to the auctions that happen when advertisers bid for displaying an ad when someone visits a webpage. This would need a massive standardization across cloud vendors, a system of penalties when the infrastructure provided by the bidder does not satisfy the characteristics, etc.

This does not too far fetched to me. It also make it easier for new cloud providers to start selling, and lower prices for developers.

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

#32

Post by redwood »

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/

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

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

#33

Post by thesandlord »

al_james wrote: post #13
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.

https://cloud.google.com/storage/transfer/

Ingress is free on all major clouds, but you still have to pay to get the data out.

(I work on GCP)

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

#35

Post by sdflkd »

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…

I just saw this today: https://zeit.co/now#frequently-asked-questions

I haven't had enough time to read into it (nor do I have enough experience to evaluate), but it seems like what you're talking about?

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

#36

Post by tyingq »

hobofan wrote: post #7
pdog wrote: post #3

Why?

The first paragraph tells you why.

Sort of. "Spread Critical Workloads" is somewhat silly to me. The uptime will be lower than the worse of the two clouds, complexity higher, and cost higher due to egress for cloud to cloud.

I do get the use case for actual multi-cloud, where there aren't cross cloud dependencies.

This setup seems unwise though. Maybe as a short term migration pathway, or similar.

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

#38

Post by dmourati »

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?

Inter-cloud?

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

#39

Post by sunbreak »

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…

This is happening; Cloudsmash - Decentralized VPS Cloud Open To The Public

https://bitcointalk.org/index.php?topic=1869603

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

#40

Post by nine_k »

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.
Post reply on HN