MENU
For this question refer to the HipLocal case study.
HipLocal wants to reduce the latency of their services for users in global locations. They have created read replicas of their database in locations where their users reside and configured their service to read traffic using those replicas. How should they further reduce latency for all database interactions with the least amount of effort?
Suggested Answer: C
Get Premium Professional Cloud Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
39 comments · newest first
TY
Tyisha
11 months ago
Totally agree, scaling is key for performance!
MA
Mabel
11 months ago
Wait, can Kubernetes really help with latency?
GI
Gianna
11 months ago
Firestore might not handle heavy traffic as well.
GA
Galen
11 months ago
I think Cloud Spanner is the best option here.
TA
Tayna
12 months ago
Bigtable is great for large datasets!
IS
Isadora
12 months ago
I practiced a similar question where using Kubernetes helped with scaling, but I wonder if that would actually reduce latency as much as the database migrations would.
NI
Nieves
1 year ago
I feel like Firestore in Datastore mode might be a simpler solution, but I can't recall if it really offers the performance boost we need for global users.
TI
Tijuana
1 year ago
I think migrating to Bigtable could be a good option since it’s designed for scalability, but I’m not completely confident about the read/write consistency.
CO
Coral
1 year ago
I remember we discussed how Cloud Spanner can handle global transactions with low latency, but I'm not sure if it's the best fit for this case.
CL
Clay
1 year ago
I'm leaning towards option D - moving to GKE and using a load balancer. That could help scale the application and improve overall performance, without the need for a full database migration. Seems like the least amount of effort to achieve the goal.
GA
Gabriele
1 year ago
Okay, let's think this through. The key is to reduce latency for all database interactions, not just reads. Migrating to a fully managed service like Bigtable or Cloud Spanner could help with that, but it might be a lot of effort. I'd want to explore other options first.
AZ
Azzie
1 year ago
Hmm, I'm a bit confused. The question mentions they already have read replicas set up, so I'm not sure if migrating the entire database is the best solution. Maybe there's a way to optimize the existing setup further?
NY
Nydia
1 year ago
This question seems straightforward - we just need to find the option that reduces latency with the least effort. I think migrating to a fully managed database service like Cloud Spanner or Firestore could be a good approach.
BE
Becky
1 year ago
I feel like I've seen a question about calling Freestyle Jobs in a Pipeline before, and I think it is possible.
JA
Jame
1 year ago
I'm not totally confident, but I'm leaning towards D - universal. That seems like the rule type that would cover both intra- and inter-zone traffic.
TE
Terina
1 year ago
I'm all about that Kubernetes life, but for this scenario, I think Cloud Spanner is the way to go. Managed databases are the future, my friends. Now, if only they had a 'Ludicrous Speed' option...
JE
Jeff
1 year ago
True, managed databases like Cloud Spanner can definitely improve performance.
AR
Artie
1 year ago
I think Cloud Spanner is more suitable for serving global user traffic efficiently.
DE
Delbert
1 year ago
But what about Bigtable? Wouldn't that also help with reducing latency?
AL
Aleisha
1 year ago
I agree, Cloud Spanner seems like the best option for reducing latency.
JA
Jamal
1 year ago
C) Migrate the database to Firestore in Datastore mode and use it to serve all global user traffic.
OR
Oretha
1 year ago
B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.
LO
Louann
1 year ago
A) Migrate the database to Bigtable and use it to serve all global user traffic.
RE
Regenia
1 year ago
Cloud Spanner all the way! I heard it's like the Ferrari of databases - fast, reliable, and perfect for global businesses. Although, I'd love to see a 'Turbo' mode that could really boost those latency numbers.
CR
Cruz
1 year ago
Hmm, I'm leaning towards the Cloud Spanner option too. It's designed for global-scale applications, so it should be a great fit for HipLocal's needs. Plus, it's a managed service, which means less overhead for them.
MA
Magnolia
1 year ago
Hmm, I'm leaning towards the Cloud Spanner option too. It's designed for global-scale applications, so it should be a great fit for HipLocal's needs. Plus, it's a managed service, which means less overhead for them.
TH
Thurman
1 year ago
B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.
FE
Felicidad
1 year ago
A) Migrate the database to Bigtable and use it to serve all global user traffic.
KI
Kina
2 years ago
I'm not sure about Bigtable or Firestore for this use case. They're more for non-relational data, right? I think the Kubernetes Engine option could work, but it might be overkill for just improving database latency.
GL
Glory
1 year ago
I think the Kubernetes Engine option could work, but it might be overkill for just improving database latency.
JE
Jeffrey
1 year ago
D) Migrate the services to Google Kubernetes Engine and use a load balancer service to better scale the application.
JO
Jolanda
1 year ago
I'm not sure about Bigtable or Firestore for this use case. They're more for non-relational data, right?
KI
King
1 year ago
C) Migrate the database to Firestore in Datastore mode and use it to serve all global user traffic.
SH
Shenika
1 year ago
B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.
EV
Eve
1 year ago
A) Migrate the database to Bigtable and use it to serve all global user traffic.
PA
Paris
2 years ago
Cloud Spanner seems like the best choice here. It's a fully managed relational database service with built-in global replication and low latency. Definitely worth considering.
CH
Charlene
2 years ago
I see both points, but I think option C might be a good compromise as Firestore in Datastore mode can also handle global traffic effectively.
ES
Estrella
2 years ago
I disagree, I believe option D is the way to go as using Google Kubernetes Engine can help with scaling the application efficiently.
CA
Cary
2 years ago
I think option B is the best choice because Cloud Spanner is designed for global scalability.