QuestionQ25

VerifiedDeploy scalable and highly available databases in Google Cloud

An application sends banking events to Bigtable cluster-a in us-east. You choose to add cluster-b in us-central1, and cluster-a replicates data to cluster-b.

You need Bigtable to keep accepting read and write requests when either cluster becomes unavailable, with requests automatically routed to the other cluster. Which deployment strategy should you use?

Explanation

A custom app profile using multi-cluster routing routes traffic to an available cluster in the replicated Bigtable instance. When one cluster becomes unavailable, Bigtable automatically fails over requests to another available cluster. Single-cluster routing cannot provide that automatic cluster failover.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!