Answer-first summary for fast verification
Answer: Migrate the database to Cloud Spanner and use it to serve all global user traffic.
HipLocal's existing setup uses a single MySQL instance with read replicas, which reduces read latency but not write latency. Migrating to Cloud Spanner (Option B) addresses both read and write latency globally. Cloud Spanner is a fully managed, globally distributed relational database that provides strong consistency and automatic scaling. It eliminates the need to manually manage replicas, aligns with Google-recommended practices, and requires minimal effort compared to migrating to a NoSQL database (Options A/C) or rearchitecting the application layer (Option D). Spanner's architecture inherently reduces latency for all database interactions in a global setup, making it the optimal choice.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
For the HipLocal case study, the company aims to minimize service latency for global users. They've already implemented read replicas in user locations and configured their service to direct read traffic to these replicas. What additional step should they take to further reduce latency for all database interactions with minimal effort?
A
Migrate the database to Bigtable and use it to serve all global user traffic.
B
Migrate the database to Cloud Spanner and use it to serve all global user traffic.
C
Migrate the database to Firestore in Datastore mode and use it to serve all global user traffic.
D
Migrate the services to Google Kubernetes Engine and use a load balancer service to better scale the application.
No comments yet.