Interesting. I haven't used JSON-stores because in my mind it always boils down to the question of how you would link entities together. I can't seem to get a g

Interesting. I haven't used JSON-stores because in my mind it always boils down to the question of how you would link entities together. I can't seem to get a good answer... so let me put this to you: In a standard RDBMS I would probably have a custom datatype for LatLon (or MGRS): create custom type LatLon(...) create table Person(id as int, name as string, location as LatLon) create table Shop(id as int, name as string, location as LatLon) Find everyone 10k around Macy's: select p.* from Person p inner join Shop s where s.name="Macy's" and with_distance(p.location, s.location, 10km) How would a JSON-store be better at managing this, given that with RDBMS systems you have indexes to help speed such cross-table looks?