5 ms·

Hello @joshxyz, here is the CEO of Meilisearch. I wanted to thank you for your feedback. I also wanted to confirm that several people have given us feedback on

Hello @joshxyz, here is the CEO of Meilisearch. I wanted to thank you for your feedback. I also wanted to confirm that several people have given us feedback on indexing speed problems. That is why we have decided to focus on this issue during the first quarter of 2022. We have already made a lot of progress on indexing speed, and we can't wait to show you these new capabilities with the arrival of v0.26.0. If you want another comparison table we have also made our own. https://docs.meilisearch.com/learn/what_is_meilisearch/comparison_to_alternatives.html#comparison-table https://docs.meilisearch.com/learn/what_is_meilisearch/compa...

mateusfreira 5y ago
Thanks for the reply, @qdequelen. Nice to know you guys are working on the indexing speed. That is what I missed in the "What's next?" session in the blog post. Looking forward to seeing what you guys will deliver
joshxyz 5y ago
Hi @qdequelen, thanks for that comparison table, I've never seen that before. Thank you also for putting indexing speed in your priority, I'm sure there are other people with large datasets who are also looking forward to it. It must be challenging, each search engine has their own best use cases right now, different requirements, and different trade offs. E.g. typesense requires decent amount of cpu and ram, quickwit allows s3 storage but doesn't support document update and delete operations yet, lol. Lovely progress too on each projects.
- qdequelen 5y ago
  To answer your third point. Indeed, each solution has its own positioning, which implies requirements and trade-offs. I don't know the positioning of Typesense and Quickwit so I would have difficulty speaking on their behalf. But I have the impression that Quickwit is the new Elasticsearch. In the long term, they will surely position themselves in front of them, put themselves on the log market, and why not of the security analysis. It is impossible to update or delete data makes me think of this. A system capable of managing terabytes of data with precise and fast tasks. Even if it is far from the need of instant search. On our side, we have a clear focus on user-facing search. All searches can improve the user experience and increase user satisfaction and product retention. Use cases today are mainly E-commerce, marketplace, site-search, media, SaaS application, B2C applications. The needs for these use cases are the same. Search in a fixed data type with incredible relevance and performance. Moreover, I want to underline this because I see that you mention it in your comments. At Meilisearch, we have made it a point of honor to offer a solution with the best possible developer experience. Everything we do (API, SDK, Documentation), we do it with developer experience in mind.
  - francoismassot 5y ago
    Quickwit co-founder here :) I pretty much agree with you qdequelen, Quickwit and Meilisearch are targeting 2 very different markets: user facing search for Meilisearch and what I would call "search analytics on large (almost) immutable datasets" for Quickwit. We want to handle deletes in 2022 in the form of "delete by query" but it will be quite a heavy operation and you won't be able to do that too often (few times per day typically). So yes, log market is one of our target, plugging Quickwit search to ClickHouse was also pretty fun. And as concerning the "best possible developer experience", Meilisearch is very inspiring and we want to follow the same path :)

mateusfreira 5y ago

Thanks for the reply, @qdequelen. Nice to know you guys are working on the indexing speed. That is what I missed in the "What's next?" session in the blog post. Looking forward to seeing what you guys will deliver

joshxyz 5y ago

Hi @qdequelen, thanks for that comparison table, I've never seen that before. Thank you also for putting indexing speed in your priority, I'm sure there are other people with large datasets who are also looking forward to it. It must be challenging, each search engine has their own best use cases right now, different requirements, and different trade offs. E.g. typesense requires decent amount of cpu and ram, quickwit allows s3 storage but doesn't support document update and delete operations yet, lol. Lovely progress too on each projects.

qdequelen 5y ago
To answer your third point. Indeed, each solution has its own positioning, which implies requirements and trade-offs. I don't know the positioning of Typesense and Quickwit so I would have difficulty speaking on their behalf. But I have the impression that Quickwit is the new Elasticsearch. In the long term, they will surely position themselves in front of them, put themselves on the log market, and why not of the security analysis. It is impossible to update or delete data makes me think of this. A system capable of managing terabytes of data with precise and fast tasks. Even if it is far from the need of instant search. On our side, we have a clear focus on user-facing search. All searches can improve the user experience and increase user satisfaction and product retention. Use cases today are mainly E-commerce, marketplace, site-search, media, SaaS application, B2C applications. The needs for these use cases are the same. Search in a fixed data type with incredible relevance and performance. Moreover, I want to underline this because I see that you mention it in your comments. At Meilisearch, we have made it a point of honor to offer a solution with the best possible developer experience. Everything we do (API, SDK, Documentation), we do it with developer experience in mind.
- francoismassot 5y ago
  Quickwit co-founder here :) I pretty much agree with you qdequelen, Quickwit and Meilisearch are targeting 2 very different markets: user facing search for Meilisearch and what I would call "search analytics on large (almost) immutable datasets" for Quickwit. We want to handle deletes in 2022 in the form of "delete by query" but it will be quite a heavy operation and you won't be able to do that too often (few times per day typically). So yes, log market is one of our target, plugging Quickwit search to ClickHouse was also pretty fun. And as concerning the "best possible developer experience", Meilisearch is very inspiring and we want to follow the same path :)