Failover

Q: How deeply does Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform cover failover?

Defines failover and implements regional traffic weighting, but defers active-active operation to future refactoring.

As explained in Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

Failover is the transfer of service traffic or operation from a failing component or environment to a standby replacement.

Failover transfers service traffic from failed primary resources to passive standby resources. An active-passive configuration keeps one environment serving requests while another remains ready as backup. section 9.1.2

A practical failover sequence is:

Create a duplicate passive environment in another region and manage it with infrastructure as code. section 9.1.2
Test, monitor, and observe infrastructure and applications before making changes, then debug the failed environment after traffic moves. section 9.1.2 section 9.4

Regional standby

The sundew system runs actively in us-central1 and keeps a passive duplicate in us-west1. If the active environment breaks during an IaC change, traffic moves to the passive region. section 9.1.2

How Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform covers it

Cover of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

liveBook manning.com

Read Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

100 SQL Server Mistakes and How to Avoid ThemFailover is the transfer of service from a failed or inactive primary system to a secondary system.
liveBook manning.com

Amazon Web Services in Action, Third Edition: An in-depth guide to AWSFailover is the process of transferring service responsibility from a failed or unavailable primary component to an available replacement.
liveBook manning.com

Microsoft Azure in ActionAutomatic failover is the automatic transfer of service operation to another region or component when the primary one becomes unavailable.
liveBook manning.com

Acing the CCNA Exam: Volume 1 Fundamentals and ProtocolsFailover is the transfer of an active network service or role to a standby device after the active device fails.
liveBook manning.com

PostgreSQL Mistakes and How to Avoid ThemFailover is the transition of service from a failed or unavailable primary system to a replica or alternate system.

Compare how 6 books explain failover →

Related concepts

active-passive configurationused by · An active-passive configuration is an architecture in which one environment serves traffic while a separate environment remains ready to take over after failure or for fallback.
disaster recoveryused by · Disaster recovery is the planning and execution of processes and capabilities for restoring systems, data, and services after a disruptive event.
standby taskaddressed by · A standby task is an inactive Kafka Streams task that maintains a replicated state-store copy for faster failover when an active task is reassigned.
uptimeused by · Uptime is the duration or proportion of a specified period during which a system or service is operational and available to provide its intended function.

This explainer was generated by Manning's knowledge graph from the text of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform. The section links point to the parts of the book it draws on.