[be_erik]

Is meilisearch ready for production workloads? I would love to use some of the feature set, but is the only option for HA running multiple instances and keeping them in sync?

[brunohaid]

You might want to look at https://typesense.org/ for that.

[Kerollmops]

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-safet...

[sealeck]

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]

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.

[bigtones]

We use Meilisearch in production with a 7 million article corpus - it works really well.

[iambateman]

My understanding for Meilisearch is that you need enough RAM to keep everything in memory...but you're (probably) not keeping full-text in memory for millions of articles.

Is it just searching metadata, or do you just have a setup that's beefy enough to support that level of memory?

Or am I just wrong? :D

[tpayet]

Yup it is, Meilisearch Cloud offers 99.99% SLA :)

We served billions of searches for hundreds of customers monthly