Geo Location & Spatial Searches with RavenDB–Part II–Modeling

time to read 1 min | 200 words

I mentioned in the previous post that the data is coming in a highly relational format, and that the MaxMind advice is to not load this into a relational database, because then queries take a long time. Instead, they have their own efficient binary format.

I decided to put this into RavenDB, and that brought the question, how are we actually going to work with this? How do we model the data?

In our code, we defined the following, which I guess would pretty closely match how you model the data in a relational database:



In this case, we are actually storing the whole thing as a single entry, like so:


This allows us to query things efficiently and easily. But before we can get there, we need to actually load the data in, which is the topic of my next post.