To anyone coming here wondering WTF is Tile38? First I'll tell you what it's not. It's not a replacement for PostGIS, and it's not built on top of Redis.
In my opinion PostGIS is the Swiss Army Knife of spatial data management. It's awesome! Especially for large datasets and complex queries. I use it all the time.
Tile38 uses the Redis protocol for network transport. There're some commands that loosely resemble Redis like SET and GET, but it's otherwise a completely different project. I originally forked Redis and built the functionality on top of the C codebase. https://github.com/tidwall/redis-gis, but scrapped that project.
What Tile38 is good for is very dynamic datasets where the application needs fast and simple point-in-polygon queries and streaming geofence notifications. Like vehicle pickup services, bus route services, proximity social apps, etc.
In my opinion PostGIS is the Swiss Army Knife of spatial data management. It's awesome! Especially for large datasets and complex queries. I use it all the time.
Tile38 uses the Redis protocol for network transport. There're some commands that loosely resemble Redis like SET and GET, but it's otherwise a completely different project. I originally forked Redis and built the functionality on top of the C codebase. https://github.com/tidwall/redis-gis, but scrapped that project.
What Tile38 is good for is very dynamic datasets where the application needs fast and simple point-in-polygon queries and streaming geofence notifications. Like vehicle pickup services, bus route services, proximity social apps, etc.