Why this matters
- Location features appear in ride-hailing, delivery, social check-ins, and StreamHub's live-event discovery — all share the same geospatial primitives.
- Naive latitude/longitude B-tree queries degrade at scale; purpose-built spatial indexes (R-tree, geohash grids, H3) are the difference between 5 ms and 5 s.
- Tile pyramids and vector tiles let you serve the entire planet without loading one giant image per request.
Core components of a maps platform
- Tile server — pre-rendered raster or vector tiles at zoom levels 0–20; clients request only visible tiles.
- Routing engine — directed graph of road segments with weights (distance, time, tolls); A* or Contraction Hierarchies for fast pathfinding.
- Geospatial index — R-tree, geohash prefix, or H3 hex cells for proximity and bounding-box queries.
- Reverse geocoder — converts coordinates to human-readable addresses using a spatial + text index.
- Traffic overlay — real-time speed data merged into routing weights via streaming ingestion.
Tile pyramid architecture
Geospatial maps architecture
Clients request map tiles by zoom level and tile coordinates (z, x, y). At zoom 0 the world is one tile; each level quadruples tile count.
GET /tiles/14/4821/6156.pbf
Host: tiles.streamhub.com
Accept: application/vnd.mapbox-vector-tile
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 4 sections
- Routing graph design
- Geospatial indexing for POIs
- Scale estimates for StreamHub maps
- Failure modes and mitigations
Test yourself
Answer these before moving on — recall is what makes it stick.