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

51–60 of 62 posts

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

#51

Post by dotancohen »

paulddraper wrote: post #45
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.

Even 9/10 of the cloud market is huge, and it's growing. I do see the OP's vision happening.

Don't forget that Apple's initial goal in the phone market was 1%.

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

#52

Post by tyingq »

discodave wrote: post #48
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.

I suppose. The downsides seem large enough that I would try and find alternative implementations such that I could do it in one cloud. Or ar least something that highly minimized cross provider dependencies and expensive data xfer.

You're fighting the purpose built intention of the cloud to make it costly and clunky to move data out.

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

#53

Post by nine_k »

hueving wrote: post #50
optimuspaul wrote: post #41

Earlier quoted context omitted.

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.

Egress is not that expensive. You use it to serve the customers, in the end.

But it's (still) too expensive to allow migration between cloud providers e.g. on hourly, or even daily, basis. That is, it prevents the consumers from realizing the benefits of short-lived spot prices.

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

#54

Post by _jal »

brianwawok wrote: post #29
tlarkworthy wrote: post #20

Earlier quoted context omitted.

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.

Really depends on the business model. I modeled different deployment scenarios for a product for a small company, and egress pricing broke the economics for the ones involving cloud providers. (It was principally concerned with hires images.) That was some time back and I know pricing has come down, so that may be different now.

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

#55

Post by masuo »

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.

Were you using a Lambda integration? I found the following blog to be useful: https://aws.amazon.com/blogs/compute/error-handling-patterns...

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

#56

Post by m3adow »

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…

Deutsche Börse created such a company a couple of years ago. Didn't go well, was shut down last year I think. I don't know how thorough the implementation was though.

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

#57

Post by whiskers08xmt »

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…

While only solving the storage part of the equation, checkout projects like Sia Coin[0] and Storj[0]. Both of them aim to provide hyper-competition for storage space, through the use of blockchain technology. I think a future, where multiple blockchain projects provide access to computational resources, isn't too farfetched.

[0] http://sia.tech/

[1] https://storj.io/

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

#58

Post by brianwawok »

_jal wrote: post #54
brianwawok wrote: post #29

Earlier quoted context omitted.

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

Really depends on the business model. I modeled different deployment scenarios for a product for a small company, and egress pricing broke the economics for the ones involving cloud providers. (It was principally concerned with hires images.) That was some time back and I know pricing has come down, so that may be different now.

> It was principally concerned with hires images

That sounds kinda like the CDN example in my case :) I guess you could amend it to say "any kind of large media files"

But even if your business does do a lot with huge media files... no reason you can't do 95% of your business on AWS or GCE, and then just offload the giant file download piece to some unlimited bandwidth server you rent.

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

#60

Post by doubleplusgood »

datums wrote: post #19
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

Thank you for sorting the operands, my OCD is satisfied
Post reply on HN