MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
1–10 of 116 posts
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#2The goal of ElasticSearch, I always thought, was that it scales horizontally and can handle the loss of multiple nodes without availability- or data-loss. It's interesting to build a single-server replacement, and this can likely work for many use-cases, but it's definitely a different approach from ElasticSearch itself.
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#3The goal of ElasticSearch, I always thought, was that it scales horizontally and can handle the loss of multiple nodes without availability- or data-loss. It's interesting to build a single-server replacement, and this can likely work for many use-cases, but it's definitely a different approach from ElasticSearch itself.
Replication for MeiliSearch is on its way :) The main differentiator is that MeiliSearch algorithms are made for end-user search not for complex queries. MeiliSearch focus on site search or app search, not analytics on hyper large datasets
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#4The real power of Elasticsearch for me is the ability to filter logs by:
1. exact match this nested JSON field (with support for lists of values)
2. negative match this nested JSON field (with support for lists of values)
coupled with the ability to filter by "timeframe", then pump it through to visualizations (tables/graphs) in Kibana
MeiliSearch would be cool if it spoke the API Kibana expects from Elasticsearch
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#5The goal of ElasticSearch, I always thought, was that it scales horizontally and can handle the loss of multiple nodes without availability- or data-loss. It's interesting to build a single-server replacement, and this can likely work for many use-cases, but it's definitely a different approach from ElasticSearch itself.
Replication for MeiliSearch is on its way :) The main differentiator is that MeiliSearch algorithms are made for end-user search not for complex queries. MeiliSearch focus on site search or app search, not analytics on hyper large datasets
what is the size of the largest dataset that you have indexed with MeiliSearch?
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#6Are the documents stored on disk or only in memory?
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#7Hardly an "alternative to Elastic search" if only because the later is scalable beyond a single machine.
This overhyped description coupled with on-by-default analytics suggests to me MeiliSearch should be dismissed regardless of potential usefulness or technical merit.
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#8Earlier quoted context omitted.
Replication for MeiliSearch is on its way :) The main differentiator is that MeiliSearch algorithms are made for end-user search not for complex queries. MeiliSearch focus on site search or app search, not analytics on hyper large datasets
what is the size of the largest dataset that you have indexed with MeiliSearch?
We are currently working with this dataset: https://data.discogs.com/?prefix=data/2020/
It's a dataset of 107M songs, 7.6 Gb of compressed files which represents 250 Gb of disk usage by MeiliSearch. We are indexing the release, song and artists names.
We also work with a dataset of 2M cities that we can index in less than 2 minutes when the db uses 3 shards.
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#9Are the documents stored on disk or only in memory?
We are using LMDB as the key/value store, so the documents are memory-mapped (usually on disk, and in memory when needed)
Re: MeiliSearch: Zero-config alternative to Elasticsearch, made in Rust
#10Hardly an "alternative to Elastic search" if only because the later is scalable beyond a single machine. This overhyped description coupled with on-by-default analytics suggests to me MeiliSearch should be dismissed regardless of potential usefulness or technical merit.
The analytics seem pretty benign.
"We send events to our Amplitude instance to be aware of the number of people who use MeiliSearch. We only send the platform on which the server runs once by day. No other information is sent. If you do not want us to send events, you can disable these analytics by using the MEILI_NO_ANALYTICS env variable."