Design Proximity Service

1. Problem Statement

2. Architecture Discussion Map

Use this as one discussion aid, not a single correct answer. Your design should follow from the requirements, scale, and trade-offs you establish.

graph LR
    A["Design Proximity Service"]
    A --> F1["Spatial Indexing Geohash vs QuadTree"]
    A --> F2["Replication vs Geographic Sharding"]
    A --> F3["Read vs Write Patterns Read-Heavy Static Places"]
    A --> F4["Accuracy vs Performance trade-offs"]

3. Key Focus Areas

• 1
  Spatial Indexing (Geohash vs QuadTree)
• 2
  Replication vs Geographic Sharding
• 3
  Read vs Write Patterns (Read-Heavy Static Places)
• 4
  Accuracy vs Performance trade-offs

4. What the Interviewer Looks For

The interviewer probes these areas, and the report grades the interview against them.

• Requirements and capacity
• Spatial indexing strategy
• Serving architecture and hot regions
• Freshness, updates, and filtering
• Moving-driver extension (assess only if reached)