Your company runs their internal services across two datacenters in a hot-warm configuration The back-end system for a new API runs in both data…

The most appropriate and standard method in Apigee to implement a hot-warm (active-passive) failover is by using the built-in load balancing capabilities of the TargetEndpoint. This involves defining each datacenter endpoint as a TargetServer. Within the TargetEndpoint's LoadBalancer configuration, the warm datacenter's TargetServer is marked with the true property. Apigee will then direct all traffic to the primary (hot) server(s). If the health monitor detects that all primary servers are unavailable, Apigee automatically fails over and routes traffic to the designated fallback (warm) server. This declarative approach is the intended design pattern for this scenario.

A. Using a Java Callout is an overly complex, imperative approach that bypasses Apigee's built-in, optimized routing features, making the proxy harder to maintain and less performant.

B. A FaultRule's primary purpose is to catch errors and return a customized error response to the client, not to re-route the original request to a different backend.

C. Service Callouts are designed for invoking external services from within a proxy flow (e.g., for enrichment), not for handling the primary target request and its failover logic.

1. Google Cloud

Apigee Documentation

"Load balancing across backend servers": This official documentation explicitly describes the use of fallback servers for failover scenarios. In the section "Configuring fallback servers

" it states

"When Apigee determines that all your primary servers are unavailable

it automatically routes all traffic to your fallback servers...". The provided XML configuration example clearly shows the use of the true element within a definition to designate a server for failover.

Reference Location: Google Cloud > Apigee > Documentation > Reference > API proxy configuration reference > Endpoint properties reference > Load balancing across backend servers.

2. Google Cloud

Apigee Documentation

"TargetEndpoint configuration": This document details the structure of a TargetEndpoint. The element is shown as a child of

and it supports one or more elements. This confirms that load balancing and server definition are integral parts of the TargetEndpoint configuration

which is the correct place to manage backend routing and failover.

Reference Location: Google Cloud > Apigee > Documentation > Reference > API proxy configuration reference > Endpoint properties reference > TargetEndpoint configuration.