|
|
|
|
|
by jdcarr
3081 days ago
|
|
The last time this was posted a few commenters mentioned using PostGIS instead of Uber rolling this themselves. If anyone's used PostGIS with a similar level of traffic/latency requirements could you comment on your experience? |
|
Query-wise, PostGIS should be able to use geohashes which can do these lookups in O(1) time (S2 geometry would be similar). That said, indexing scales terrible with geohashing/S2 at high granularity levels, though they wouldn't need something particularly granular for this (seems fine to be off by tens or hundreds of meters)