whoosh VS minisearch

The only other embeddable search engine I'm aware off, Whoosh, is brilliant but building the index was quite slow, and search performance degraded quite a lot as number of documents increase (performance is strictly a non-goal). Meilisearch was comparatively faster, I didn't like managing a server to get "just search" in my scripts and applications. However, their underlying engine Milli solves both issues I had, and all that was needed creating bindings for it.

Is it really "just a single statically linked binary"?

I'd love to use Meilisearch as you describe, but their so-called SDKs are just about for the search client, you still need the HTTP server listening on localhost.

I would love to see something like SQLite based off Meilisearch (i.e. a fully selfcontained library like https://github.com/mchaput/whoosh). Do you know if such a thing exists?

For our full text search, we used whoosh, which works pretty well for moderately big amount of data.

Nearly a decade ago (oh god) I converted some overdesigned five node ES mess to https://github.com/mchaput/whoosh. It's (obviously) not the fastest or anything, but it was more than good enough for low-dozens of GBs of mostly static data.

Your best bet is to start using a proper search library rather than the simple loop with 'in' checks that you have now. A search lib will handle things like Unicode/ASCII similarities, removal of stop words, stemming, TF-IDF (and other) weighting, etc. and will be massively faster as well. Quite a few pages come up if you Google "python search engine", also Whoosh looks promising.

I wrote an online catalog a while back (and I need to get back on adding graphics and products at some point). It’s written using Eleventy and the minisearch library. The source and data are available on Github if you want to see how I did things. I’m not a professional web designer either, but it was a fun project.

You could have a look at https://github.com/lucaong/minisearch/

If you're dealing with thousands of records or less, searching titles and summaries rather than long bodies of text, I recommend looking into client-side solutions. Nothing beats the responsiveness of search-as-you-type entirely on the client side. It can be fairly sophisticated fulltext search. For example, I've built had great success with MiniSearch.

I quite enjoy minisearch[1] which is also 0 dependencies, actively maintained, and I expect would work well in a worker environment. I dropped it into a service worker and plugged it with a simple point in polygon script to enable geosearch for a recent project[2] and it played v. nicely.

[1] https://github.com/lucaong/minisearch

No magic here, the underlying engine is Minisearch, which uses the BM25 algorithm (the de facto standard among search libraries). Omnisearch adds a magic sauce during indexing by converting notes into custom objects, with the following fields: - body (the plain markdown text) - filename & yaml aliases - level 1 headers - level 2 headers - level 3 headers

It's actually really simple! Minisearch did most of the heavy lifting so all we needed to do was the crawling, storing and UI etc. I'd check that out if you're interested in the search part!

We use MiniSearch for searching, while fast-fuzzy is used for highlighting of detected search terms.