One of the fun parts about RavenDB is that it will self optimize itself for you depending on how you are using your data.
With this blog, I decided when going live with RavenDB that I would not follow the best practices of ensuring static indexes for everything, but would let it figure it out on its own.
Today, I got curious and decided to check up on that:
What you see is pretty interesting.
- The first three indexes were automatically created by RavenDB in response to queries made on the database.
- The Raven/* indexes are created by RavenDB itself, for the Raven Studio.
- The MapReduce indexes are for statistics on the blog, and are the only two that were actually created by the application explicitly.