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.
Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
21–30 of 62 posts
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#22Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#23why 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
#24this 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
#25A (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
#26This 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.
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#27why 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.
Just take your own rest backend and put cloudfront on it and it you'll have more functionality and as much or more scalability and security, for an "api".
Re: Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda
#28why 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
#29this 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?