I have a very limited but significant use case for spatial index in a routing service. I see these indexes not growing beyond 10,000 geometries for the next 1 year and maybe 100,000 for the next 3 years. The solution needs to be approached from a delivery timeline perspective mostly because the use case also comes with a slightly relaxed compute time SLA and cost optimum implementation PoV.

We have chosen R-Tree based index as a suitable choice for our use case. We are already using Aerospike and MySQL in our stack. MySQL supports R-Tree and has good docs as well. I couldn't find anything specific to R-Tree with Aerospike. Also, generally would like to understand from the performance perspective how these two choices would fare with something like Tile38?

Suggestions beside these are also most welcome.