These both seem to be very active and fairly popular elastic search gems for rails. It seems like the major difference is that searchkick has more customization based on individual users.
What are the differences that one would want to consider before choosing which one to use?
https://github.com/elasticsearch/elasticsearch-rails
*s 872
fork 165
latest commit 2.5 months ago
https://github.com/ankane/searchkick
*s 1,594
fork 165
latest commit 11 days ago
Search kick Gem is a Ruby gem that runs on top of Elasticsearch and makes it easy to make searches in a Rails-friendly fashion. In addition, it allows you to add more features including analytics, autocomplete, and personalized results. Searchkick realizes what your users are searching for.
Elasticsearch (ES) is a powerful Full Text Search Engine based on Apache Lucene. A key characteristic of Elasticsearch is that it's distributed at it's core, meaning that you can easily scale it horizontally for the purpose of redundancy or performance.
It decides the structure of our fields and mappings based on our model attributes. Searchkick also handles automatically updating our index when we add new records or change existing records. Without searchkick we would 'manually' have to issue requests to elasticsearch via the http api.
Searchkick is much more Rails friendly gem, they have features to get autocomplete for example and don't force you to learn guts of ElasticSearch to do basic stuff.
Also, looks like guy who wrote searchkick use it himself in Rails vs Elasticsearch-rails is just library for one more language for ElasticSearch team.
I started with Elasticsearch-rails and migrated to searchkick myself.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With