4 ms·

Thanks for sharing, we did do a POC of it in the company I work for as an alternative for elastic-search, and it worked pretty well(in most cases). Unfortunate

Thanks for sharing, we did do a POC of it in the company I work for as an alternative for elastic-search, and it worked pretty well(in most cases). Unfortunately, we end up not moving forward with it because we need new ingestion to be available super quickly. I hope to see new versions improving that too. Thanks for the list of competitors. I will take a look at them

joshxyz 5y ago
Similar exp lol. I was instantly sold at the ease of installation, great documentation, and the built-in search interface web app. Had to put it on the side for a while when I noticed it just indexed 3m docs in 8hrs (compared to 70m docs in 8 hrs of same data on elasticsearch). There were tips given on their slack but we found it a bit too hacky (at that moment) for our use case (you know, worries that will such approach be consistent or broken on next versions, things like that). Nevertheless I still think it's perfect for hundreds of thousands of documents at the moment (just not millions yet).
- qdequelen 5y ago
  Indeed for the moment, I would not advise going to more than a few million documents, especially if you want to make regular updates. With the new update that we will release in March, I think we will go up to a few tens of millions of documents with much higher update frequencies. However, we keep in mind that Meilisearch should do much, much more. This will be a work in progress for us during the year, as we plan in the future to allow Meilisearch to be no longer a search binary with limited resources but as a globally distributed solution that will have no limits to scale. But it's still too early to talk about our long-term plans on how we will improve user-facing search. #serverless