Searchkick VS Elasticsearch Rails

I run a large scale production application that does something along these lines. If the data needs to be close to real-time, I'd say use `searchkick` + Elasticsearch, and use `searchkick`'s async feature to "stream" the data from your table to the ES index. Your dashboard will then just query from the ES index via searchkick.

You're right, that's actually what we implemented, application-level hooks, but they needed development and maintenance effort that come for free with the adapter we're using for OpenSearch integration, which also comes with welcome features: synonyms, partial matches, and many others.

Spoiler, the adapter is Searchkick: https://github.com/ankane/searchkick

Searchkick

Convinced? Ok read on and I’ll show you what switching from Elasticsearch to Meilisearch looked like for a real production app — ScribeHub. We also moved from Ankane’s excellent Searchkick gem to the first party meilisearch-rails gem and I’ll show you the changes there as well.

If you want to use a look-aside pattern (like you might have used with Searchkick + Elasticsearch), you should check out ActiveStash: https://github.com/cipherstash/activestash

Searchkick learns what your users are looking for. As more people search, it gets smarter and the results get better. It’s friendly for developers - and magical for your users. BONUS: it's written and supported by "ankane" who has flawless reputation amongst the Ruby community.

Let's add Elasticsearch into the mix. To do so, we will need the elasticsearch-model gem. It's an official Elasticsearch gem that integrates nicely with Rails models.

I like Elasticsearch a lot (Lucene’s architecture is awesome), there should be plenty of Rails gems that can interface with it. https://github.com/elastic/elasticsearch-rails