4 ms·

Meilisearch has been production-ready since v1.0. I made it in Rust to ensure it stays production-ready for years and years. Memory-safe languages are here to r

Meilisearch has been production-ready since v1.0. I made it in Rust to ensure it stays production-ready for years and years. Memory-safe languages are here to replace unsafe ones like C++ and reduce the number of breaches you expose in production. Here is an article by Google showing the benefits of using memory-safe languages in production rather than others. It is explicitly rotating around Rust [1]. [1]: https://www.chromium.org/Home/chromium-security/memory-safety/ https://www.chromium.org/Home/chromium-security/memory-safet...

sealeck 1y ago
Writing software in Rust doesn't necessarily mean that it works reliably for real-world workloads. Sure, Rust prevents you from doing lots of stupid things; it is very much in the class of "necessary but not sufficient condition" for writing software (of course, you can also use other languages, but memory safety should be table stakes for all software these days).
arccy 1y ago
This reply doesn't inspire confidence at all... Made in Rust isn't a magic bullet to be production ready, and I'd be more concerned about logic bugs rather than CVEs. 1.0 is like the bare minimum to be used in production, but that doesn't necessarily mean it's been battle tested enough to be considered production ready.
- Kerollmops 1y ago
  HuggingFace is using Meilisearch, in production, on their website for a year now.
  - holysantamaria 1y ago
    And it takes 360ms to get an answer from their server (not fulltext, quicksearch api endpoint). And 2ms to download the results on the network. Is this the instant search that you are advertising on your website?
    - Kerollmops 1y ago
      V1.14, released yesterday [1], ships with a search embedding cache. Most of the time you see is spent waiting for an OpenAI embedding answer. We also just shipped composite embedders to reduce the network latency when you need to respond quickly to user searches (by running embedders on the Meilisearch server) but still use external APIs to index many documents in batches. Note that it can only work with open-source embedders, the ones HuggingFace serves. [1]: https://github.com/meilisearch/meilisearch/releases/tag/v1.14.0 https://github.com/meilisearch/meilisearch/releases/tag/v1.1...

sealeck 1y ago

Writing software in Rust doesn't necessarily mean that it works reliably for real-world workloads. Sure, Rust prevents you from doing lots of stupid things; it is very much in the class of "necessary but not sufficient condition" for writing software (of course, you can also use other languages, but memory safety should be table stakes for all software these days).

arccy 1y ago

This reply doesn't inspire confidence at all... Made in Rust isn't a magic bullet to be production ready, and I'd be more concerned about logic bugs rather than CVEs. 1.0 is like the bare minimum to be used in production, but that doesn't necessarily mean it's been battle tested enough to be considered production ready.

Kerollmops 1y ago
HuggingFace is using Meilisearch, in production, on their website for a year now.
- holysantamaria 1y ago
  And it takes 360ms to get an answer from their server (not fulltext, quicksearch api endpoint). And 2ms to download the results on the network. Is this the instant search that you are advertising on your website?
  - Kerollmops 1y ago
    V1.14, released yesterday [1], ships with a search embedding cache. Most of the time you see is spent waiting for an OpenAI embedding answer. We also just shipped composite embedders to reduce the network latency when you need to respond quickly to user searches (by running embedders on the Meilisearch server) but still use external APIs to index many documents in batches. Note that it can only work with open-source embedders, the ones HuggingFace serves. [1]: https://github.com/meilisearch/meilisearch/releases/tag/v1.14.0 https://github.com/meilisearch/meilisearch/releases/tag/v1.1...