Multi-Cloud: the practice of utilizing multiple cloud computing services to host your infrastructure.

  • Why should I use this?

The main purpose of multi-cloud deployments is to mitigate against disasters that were not in your control: if a service such as AWS or GCP becomes unresponsive or critically fails, your infrastructure and applications can redirect traffic and user access to other cloud services that are still up and running.

Another use for multi-cloud deployments is to avoid vendor lock-in; if your company decides later on that one cloud provider is pushing heavy-handed rules and regulations onto your deployments it can be extremely costly to switch providers especially if your tools and services have become increasingly dependent on one provider. If your infrastructure is configured to work on multiple services already it should be a far simpler matter to cut ties with a service provider as needed.

  • But what does this have to do with Spinnaker?

Spinnaker allows for easy configurations of a pipeline to execute a multi-cloud deployment as well as keep track of the execution’s progress. We have a short demonstration video here.

  • What companies actually use this?

As an example, Nir Tarcic, Site Reliability Engineer at Waze, gave a talk at Google Next where he said that multi-cloud deployments would not have been possible without Spinnaker, and that "Spinnaker saved us 1,000 people.”

Details about Waze’s experience with Google Cloud Platform and Spinnaker can be found here.

This post is part of a series of posts that describe features in Spinnaker. You can find all of the related posts here.