On 6/2/2019 7:28 AM, Ralph Soika wrote:
This is not intended to contradict the other replies you've gotten, only
supplement them.
Now as far as I understand is solr a cluster enabled datastore which can
be used to store also all the data form our document.
The problem with relational databases was always the lack of
cloud/cluster support to get more stable data by using redundancy over
serveral nodes.
At it's heart, Solr is using something you already understand -- Lucene.
Certain functionality is implemented above that in Solr -- facets
being probably the primary example. For the most part, if you wouldn't
use Lucene for some purpose, you shouldn't use Solr for that purpose
either -- because Solr is written with the Lucene API.
Search is Solr's primary function, and what it is optimized to do. Any
other use, even when it is possible, is probably going to be better
handled by another piece of software.
We have done what we can to eliminate problems that lose data, but data
retention in the face of all potential problems is not one of the design
goals. Things CAN go wrong that result in data loss ... while most
database software is hardened against data loss from even unexpected
problems.
What do you think? Is solr an alternative to store and index data
instead of useing Lucene in combination with RDBMS?
In general, no. There are things databases can do that Solr can't, and
some things that a database is better at than Solr is. Solr is good at
search, and things related to search.
If you have the system resources, putting a complete copy of your data
in Solr is not necessarily a bad thing. Some amazing things can be done
in the arena of data mining. The facet feature that I mentioned above
tends to be very usable for that.
Thanks,
Shawn
