Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
cloudplatform.googleblog.com
Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
1–10 of 62 posts
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#2This is very wise advise to those on a certain "forest" cloud
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#3Why?
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#4clickbait. I don't consider this multi-cloud
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#5TL;DR - call services on GCP from your AWS lambda functions using Cloud Endpoints.
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#6[deleted]
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#7Why?
The first paragraph tells you why.
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#8this 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?
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#9this 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?
Nope, spot on. You either cache extremely aggressively with a CDN if you can, or otherwise you eat the data out charges for dynamic data.
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#10This 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.