On 4/4/2022 5:52 AM, Srijan wrote:
I am working on designing a Solr based enterprise search solution. One requirement I have is to track crawled data from various different data sources with metadata like crawled date, indexing status and so on. I am looking into using Solr itself as my data store and not adding a separate database to my stack. Has anyone used Solr as a dedicated data store? How did it compare to an RDBMS?
As you've been told, Solr is NOT a database. It is most definitely not equivalent in any way to an RDBMS. If you want the kinds of things an RDBMS is good for, you should use an RDBMS, not Solr.
Handling ever-changing search requirements in Solr is typically going to require the kinds of schema changes that need a full reindex. So you probably wouldn't be able to use the same Solr index for your data storage as you do for searching anyway.
If you're going to need to set up two Solr installs to handle your needs, you should probably NOT use Solr for the storage role. Use something that has been tested and hardened against data loss. Solr does do its best to never lose data, but guaranteed data durability is not one of its design goals. The changes that would be required to make that guarantee would most likely have an extremely adverse effect on search performance.
Solr's core functionality has always been search. Search is what it's good at, and that's what will be optimized in future versions ... not any kind of database functionality.
Thanks, Shawn
