3 ms·

Im wondering what are the use cases here. Why someone would keep different functions in different providers while she requires the communication between them.

Myztiq 9y ago
I'm not entirely sure myself, a few guesses. * Cost based configurations * Putting high compute in one cloud and storage in another? * Perhaps to handle entire cloud outages? * There may be features that don't exist across all the providers that people may want to take a dip into. * Integration w/ existing frameworks, AKA code deployed to multiple clouds that need to be supported.
- deleted 9y ago
  [deleted]
nichochar 9y ago
The example given at the emit conference was: You have a lot of code running in AWS, but all of a sudden, you would like to start using some nice features around google ML, and for this you need integration with google cloud. Over a longer period, the idea is that there is an oligopoly of PaaS providers and if their features don't match 1:1 perfectly, your business may need a hybrid approach.
- mayank 9y ago
  > The example given at the emit conference was: You have a lot of code running in AWS, but all of a sudden, you would like to start using some nice features around google ML, and for this you need integration with google cloud. I'm at the conference, and this isn't a great example. You don't need to set up a Google Cloud Function to use the Google ML APIs (or pretty much any Google APIs), you can just use them over the REST API.
  - ApolIlo 9y ago
    Multi-cloud use case has a very niche use. I have a very few clients that use multi-cloud strategy but when they do it's very structured. Certain workloads use certain providers and those services have auxiliary services that reside very near for performance and cost efficiencies. But yes I agree. Not the best example. - I'm a the conference as well
  - wyattjoh 9y ago
    I think an advantage could be if you wanted to push the message from a lambda function into a google cloud pub sub topic which a google cloud function would consume possibly?
    - deleted 9y ago
      [deleted]

Myztiq 9y ago

I'm not entirely sure myself, a few guesses. * Cost based configurations * Putting high compute in one cloud and storage in another? * Perhaps to handle entire cloud outages? * There may be features that don't exist across all the providers that people may want to take a dip into. * Integration w/ existing frameworks, AKA code deployed to multiple clouds that need to be supported.

deleted 9y ago
[deleted]

nichochar 9y ago

The example given at the emit conference was: You have a lot of code running in AWS, but all of a sudden, you would like to start using some nice features around google ML, and for this you need integration with google cloud. Over a longer period, the idea is that there is an oligopoly of PaaS providers and if their features don't match 1:1 perfectly, your business may need a hybrid approach.

mayank 9y ago
> The example given at the emit conference was: You have a lot of code running in AWS, but all of a sudden, you would like to start using some nice features around google ML, and for this you need integration with google cloud. I'm at the conference, and this isn't a great example. You don't need to set up a Google Cloud Function to use the Google ML APIs (or pretty much any Google APIs), you can just use them over the REST API.
- ApolIlo 9y ago
  Multi-cloud use case has a very niche use. I have a very few clients that use multi-cloud strategy but when they do it's very structured. Certain workloads use certain providers and those services have auxiliary services that reside very near for performance and cost efficiencies. But yes I agree. Not the best example. - I'm a the conference as well
- wyattjoh 9y ago
  I think an advantage could be if you wanted to push the message from a lambda function into a google cloud pub sub topic which a google cloud function would consume possibly?
  - deleted 9y ago
    [deleted]