Companies like Yahoo, Google, MS provide geocoding services. I'd like to know what is the best way to organize the backend for such services - what is the optimal solution in terms of database provider(SQL vs NOSQL) and database schema.Some providers use \[code\]Extensible Address Language (xAL)\[/code\] to describe an entity in the geocoding response. xAL has more than 30 data elements. Google geocoding API has about 20 data elements.So in case of SQL database there will be 20-30 tables with mostly one-to-many relationships via foreign keys?What about NOSQL databases, like MongoDB. How would one organize such a database? lots of collections for each data element, similar to SQL? One collection where each document completely describes given entity in the address space?
geocoding database provider(sql, nosql) and schema
- Thread starter Intancady
- Start date