Join the DZone community and get the full member experience.
Join For FreeRavenDB vs MongoDB: Which is Better? This White Paper compares the two leading NoSQL Document Databases on 9 features to find out which is the best solution for your next project.
So after I finished telling you how much I don’t like the Lucene.net codebase, what's this post about?
Well, I don’t like the code, but then again, I generally don’t like to read low-level code. The ideas behind Lucene are actually amazingly powerful in their simplicity.
At its core, Lucene is just a set of sorted dictionaries on disk (greatly simplified, I know). Everything else is built on top of that, and if you grok what is going on there, you would be quite amazed at the number of things that this has made possible.
Indexing in Lucene is done by a pipeline of documents and fields and analyzers, which all participate together to generate those dictionaries. Searching in lucene is done by traversing those dictionaries in various ways, and combining the results in interesting ways.
I am not going to go into details about how it works, you can read all about that here. The important thing is that once you have grasped the essential structure inside lucene, the rest are just details.
The concept and the way the implementation fell out are quite beautiful.
Do you pay to use your database? What if your database paid you? Learn more with RavenDB.
Like This Article? Read More From DZone
Published at DZone with permission of Oren Eini, CEO RavenDB , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}