reactivesearch VS Typesense

The SearchBox component is part of the ReactiveSearch UI kit: https://github.com/appbaseio/reactivesearch and works with Elasticsearch, OpenSearch, Solr, and MongoDB Atlas Search as search engine backends. Support for OpenAI is coming soon - star or watch the repo to be in the loop for this one.

reactivesearch has the most stars from what I can find on GH. I've never used one either, maybe someone else will have a better suggestion.

This is a follow-along post (takes a couple of hours to build this end-to-end) showing how to build a consumer grade search UI using React and Elasticsearch. It makes use of the https://github.com/appbaseio/reactivesearch library (Apache 2.0 licensed) that's being used by over 1,000 projects for building their search UI.

It kinda depends what you have and what you want out of it, for https://demo.rapidez.io/women/tops-women we use Reactivesearch (Vue variant): https://opensource.appbase.io/reactivesearch/

🤩 Reactive Search- UI components for building data-driven search experiences.

ReactiveSearch - UI components library for Elasticsearch

There are actually plenty of non-ES products that are way easier to integrate and tune (and get better results with less effort).

- Typesense (https://github.com/typesense/typesense)

- Algolia

- Google Programmable Search Engine (https://programmablesearchengine.google.com/about/)

Typesense - Open Source Alternative to Algolia

If you like your penny take a look at Typesense https://typesense.org/ - nothing to complain here. Especially nothing complain about pricing.

I work on Typesense [1] (historically considered an open source alternative to Algolia).

We then launched vector search in Jan 2023, and just last week we launched the ability to generate embeddings from within Typesense.

You'd just need to send JSON data, and Typesense can generate embeddings for your data using OpenAI, PaLM API, or built-in models like S-BERT, E-5, etc (running on a GPU if you prefer) [2]

You can then do a hybrid (keyword + semantic) search by just sending the search keywords to Typesense, and Typesense will automatically generate embeddings for you internally and return a ranked list of keyword results weaved with semantic results (using Rank Fusion).

You can also combine filtering, faceting, typo tolerance, etc - the things Typesense already had.

[1] https://github.com/typesense/typesense

[2] https://typesense.org/docs/0.25.0/api/vector-search.html

For something small with a minimal footprint, I'd recommend Typesense. https://github.com/typesense/typesense

I haven’t used Publish, but I’d assume you could use something like https://typesense.org/ to index and search the vault.

A cheaper option would be to use https://typesense.org. You can use DynamoDb streams to automatically load records. It has worked well for me.

Try tigris | typesense for faster search

I’m also checking out Typesense as a possibility for replacing Elastic: https://typesense.org/