3 ms·

How would it compare to something like https://github.com/meilisearch/meilisearch https://github.com/meilisearch/meilisearch? The main differentiator for me see

by dewey 4y ago

How would it compare to something like https://github.com/meilisearch/meilisearch https://github.com/meilisearch/meilisearch? The main differentiator for me seems to be "Compatibility with Elasticsearch API".

Thaxll 4y ago
Meilisearch does not have compatibility with ES API so why asking? The title is " lightweight alternative to Elasticsearch".
- dewey 4y ago
  There's many "lightweight alternatives" to Elasticsearch (see this thread, which lists at least two already). Alternative doesn't always mean they are API compatible, it's an alternative and not a drop-in replacement. My question was about how comparable it is apart from the API compatibility.
nindalf 4y ago
Another alternative to ES and Lucene respectively - QuickWit (https://github.com/quickwit-oss/quickwit https://github.com/quickwit-oss/quickwit) and Tantivy (https://github.com/quickwit-oss/tantivy https://github.com/quickwit-oss/tantivy).
drakerossman 4y ago
As it seems, it has near full compatibility with the Elasticsearch API. https://github.com/zinclabs/zinc/issues?q=is%3Aissue+elasticsearch+api+is%3Aclosed https://github.com/zinclabs/zinc/issues?q=is%3Aissue+elastic...
- prabhatsharma 4y ago
  @draerossman. Thanks. Yeah, indeed we have pretty decent compatibility with ES.
shimonamit 4y ago
Or https://github.com/typesense/typesense https://github.com/typesense/typesense
- jabo 4y ago
  I work on Typesense and I can speak to it from Typesense’s perspective. Typesense holds the entire index in memory, in order to enable fast search where every keystroke returns results in 50-150ms. So it’s built primarily to enable user-facing search. It’s not a good fit for log search since putting your entire log dataset in memory can become expensive depending on the size of your logs, and you typically don’t need search-as-you-type for log search. Zinc on the other hand seems to be designed specifically for log search.

by dewey 4y ago

Thaxll 4y ago

Meilisearch does not have compatibility with ES API so why asking? The title is " lightweight alternative to Elasticsearch".

dewey 4y ago
There's many "lightweight alternatives" to Elasticsearch (see this thread, which lists at least two already). Alternative doesn't always mean they are API compatible, it's an alternative and not a drop-in replacement. My question was about how comparable it is apart from the API compatibility.

nindalf 4y ago

Another alternative to ES and Lucene respectively - QuickWit (https://github.com/quickwit-oss/quickwit https://github.com/quickwit-oss/quickwit) and Tantivy (https://github.com/quickwit-oss/tantivy https://github.com/quickwit-oss/tantivy).

drakerossman 4y ago

As it seems, it has near full compatibility with the Elasticsearch API. https://github.com/zinclabs/zinc/issues?q=is%3Aissue+elasticsearch+api+is%3Aclosed https://github.com/zinclabs/zinc/issues?q=is%3Aissue+elastic...

prabhatsharma 4y ago
@draerossman. Thanks. Yeah, indeed we have pretty decent compatibility with ES.

shimonamit 4y ago

Or https://github.com/typesense/typesense https://github.com/typesense/typesense

jabo 4y ago
I work on Typesense and I can speak to it from Typesense’s perspective. Typesense holds the entire index in memory, in order to enable fast search where every keystroke returns results in 50-150ms. So it’s built primarily to enable user-facing search. It’s not a good fit for log search since putting your entire log dataset in memory can become expensive depending on the size of your logs, and you typically don’t need search-as-you-type for log search. Zinc on the other hand seems to be designed specifically for log search.