Learn all you need to know about email best practices, deliverability, and tools with email whitepapers and ebooks.

Issue link: https://hub.dyn.com/i/1119883

Contents of this Issue


Page 12 of 57

Figure 1-2. Active-passive multicloud architecture In an active-passive architecture, the backup site is "hot," the infra‐ structure is online and listening, but no traffic is directed to that cloud provider unless the failure occurs. Active-passive architec‐ tures are more cost-effective than active-active multicloud environ‐ ments, but there are a number of technical complexities that need to be taken into consideration. First and foremost, the infrastructure must be tested regularly to ensure seamless failover in the event of a failure at the primary site. The infrastructure of the passive site must be treated as if it were live. You can take advantage of the fact that you have a fully functional replication of your website or web appli‐ cation by testing new patches and configurations on the passive site before pushing them to the live site. Public/Private Multicloud Architecture Up to this point, we have been discussing public cloud infrastruc‐ ture, but cloud infrastructure can also be private. This can be a non‐ public instance set up in a traditional cloud provider, such as Amazon or Google, or it can be a cloud instance set up in your own datacenter or colocation facility. Private cloud infrastructure is usually designed to host highly- sensitive organizational information. A private cloud instance might hold customer data, employee information, or other sensitive com‐ Modes of Distributing Workloads Across Multiple Cloud Providers | 7

Articles in this issue

view archives of eBooks - OreillyMultiCloudFinalEBOOK