Hard Design: Ride-Sharing Service (Uber/Lyft)

What database is most appropriate for storing driver location history for audit and analytics purposes?

— Tests your understanding of this concept.

Answer Options

A MySQL with spatial index

B Cassandra partitioned by driver_id, clustered by timestamp

C Redis (in-memory only)

D MongoDB with 2dsphere index

Want to see the correct answer?

Get the answer with a detailed explanation, plus practice 22+ more Design: Ride-Sharing Service (Uber/Lyft) questions with adaptive quizzes and timed interviews.

See the Answer on Guru Sishya →

This question is from the Design: Ride-Sharing Service (Uber/Lyft) topic (System Design Cases).

Learn Design: Ride-Sharing Service (Uber/Lyft) → Browse All Questions

More Design: Ride-Sharing Service (Uber/Lyft) Questions

Why is Euclidean (straight-line) distance insufficient for ETA calculation in a ride-sharing app?

Why must neighboring geohash cells also be queried when searching for nearby drivers?

A driver's phone GPS has a 30-second outage. What happens to ongoing trip tracking?

What Redis data structure is used to store driver locations by geographic cell?

How does surge pricing work and how do you ensure it's fair to riders?