12👍
Personally, I’ve used both Solr and ElasticSearch with with django haystack and have been happy with the results from both. Solr seemed to have a slightly steeper learning curve, but it wasn’t enough to be a deal breaker. If you have a cloud-based implementation in mind for your project, you may want to go with ElasticSearch as it features distributed indexing and some other useful features that kind of environment. I don’t have any experience with Xapian, so I won’t mislead you with any information there.
You may want to check out this post from the creator of ElasticSearch https://stackoverflow.com/a/2288211/1608085 (yes, it will be a bit biased)
Also check out this previous answer for a comparison of Solr and ElasticSearch
https://stackoverflow.com/a/10213568/1608085
1👍
I`ve been working in a project that uses solr to perform searches. It is a good solution.
A more extended input to this you can find here – Why use Solr
- DjangoRestFramework – Omit null fields when serializing objects
- Django template name conflict
- Django REST – Create object with foreign key using serializers
- Error: "The security token included in the request is invalid" when using Boto python
- UnicodeEncodeError：'latin-1' codec can't encode characters in position 0-1: ordinal not in range(256)
- Django Haystack update index faster
- How to represent two model fields as one form field in Django?
- Django migrate and makemigrate automatic yes on prompt