+972 52-548-6969
Geo Location & Spatial Searches with RavenDB–Part II–Modeling
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:
Except…
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.
Comments
I rather see fewer, but complete posts, instead of these part 1-5 posts which have little value on their own. These part 1-5 posts should be chapters within one big post, not posts on their own.
@Bart - While I completely agree, because by about the 3rd part I've lost interest in the series and most often never read them... If Ayende did that, he would only have about 300 posts, and not 5k+
Philip and Bart, Look at the older posts. I did that for a while, and what I found is that I have a lot more participation and interest when I break things up in this fashion
Ayende,
I never consciously thought about that but you're right.
Also: I have never postponed reading one of your articles because they are always digestible in minutes. Valuable content in manageable chunks.
Comment preview