All geek questions in one place

Building a case for solr

Our product consists of several applications: all using Lucene. 2 of the apps I'm connected to have Lucene indexes of around 3 GB and 12 GB. Another team creates an application for which they estimate the size of LUCENE INDEX close to 1 terabyte. New documents are added to indexes every 15 days. We do not have any obvious problems with current applications. So my question is:

Should we use Solr now?

When should you stop using Lucene and alumni in Solr?

Any flaws / problems for using Solr?

Client applications are created in ASP.Net, but I assume that they can use the Solr server using solrnet.

+3
source share
2 answers

I do not think that the transition from Lucena to Solra is itself a "graduation". You should use whatever is best for your particular application, while taking into account the experience of the development team.

Moving to Solr has the advantage of being easily distributed , you will need it. OTOH, if you can match the 1TB index on one machine without performance issues, then you don't need to redistribute. I do not recommend distributing if you do not need. Distribution means that you will have to support N Solr servers, and not just one, so the operational level of support is increasing. Programmatically (in the .Net application) there should not be much difference.

Solr - Lucene, , faceting, caching, ... , " , Lucene (.net), Lucene.

+7

Solr Lucene REST. , HTTP-. , Lucene , Solr - .

, , , , Lucene , Solr . , , Solr.

0

Source: https://habr.com/ru/post/1744398/

More articles:


All Articles