Meilisearch Blog

Thank you for the feedback. You should probably look at our blog post explaining how to index in smarter way [1]. You should probably come and talk to us on Discord. We work with MrBeast and they don't have any issue indexing millions of YouTube videos everyday. Ho! And just to tease you a little bit. We highly improved the indexing speed of Meilisearch v1.6 (january 24). Here is a teasing tweet [2]. [1]: https://blog.meilisearch.com/best-practices-for-faster-indexing/amp/ [2]: https://x.com/kerollmops/status/1734576622303404317

Meilisearch | https://jobs.lever.co/meili | Remote (GMT-4 to GMT +5) | 4day workweek Meilisearch is an open-source search API. We provide developers tools to implement search bars, so their users spend less time searching & more time finding. We are looking for a few different roles: - Full-stack software engineer working on the cloud offering (React, Rails, K8s) - Senior software engineer working on the core engine (Rust) - Technical community manager Salaries are location independent; you'll get equity, six weeks of PTO, and three months of paid parental leave. You can see our repositories on https://github.com/meilisearch & learn more about the company on https://blog.meilisearch.com.

You could maybe use something equivalent to the "index hot swap"[1] feature we have at the Meilisearch level at startup, so that you make the reindexing in a another index at startup, and then atomatically swap this fresh index with the old one when it is ready? That way, you have fast startup at the cost of having possibly out-of-date information for a while after startup. (you could even reindex from scratch completely in the background at startup, so no need to discover deleted files at all) [1]: https://blog.meilisearch.com/zero-downtime-index-deployment/

Since its previous version, Meilisearch is offering a finer control over typo tolerance https://blog.meilisearch.com/typo-tolerance/

Not only does it exist but they recently closed another round of funding: https://blog.meilisearch.com/meilisearch-raised-5meu-seed-fundraising/

Maybe. That one distinguishes itself from Elastic and hasn't set its sights on big data. > Elasticsearch is very powerful when it comes to massive datasets; it can quickly scale horizontally and allows one to build complex queries. The flipside of that is that nothing is easy. Even if all you need is simple search functionality that handles typos, synonyms, or filters, you're looking at hours of training, documentation, and configuration. Spending some hours learning a new tool doesn't seem so bad to me when I'll be working with it as part of my product. > For big tech companies dealing with enormous logs, Elasticsearch might make sense. But when it comes to medium-size datasets (i.e. less than five million rows) and smaller apps, it simply isn’t right for the job. Nonetheless, since no open-source alternative has historically been available, developers still go for Elastic as their default solution and wind up losing a disproportionate amount of time on setup and training. > MeiliSearch is not made to search through billions of large text files or parse complex queries. https://blog.meilisearch.com/why-should-you-use-meilisearch-over-elast… I'm not sure I'd like to assume that my dataset will never grow. This is kind of like using training wheels. Some may find it helpful but I don't think it will grow to the widespread adoption Elastic has seen without a change of vision.

Dual-licensing with a suitable public license would allow him to build a viable business. https://duallicensing.com/ https://indieopensource.com/public-private/indies EPPlus was relicensed earlier this year, and it's already generating enough revenue to pay two full-time developer salaries in Sweden. https://blog.meilisearch.com/value-in-open-2-epplus/ The Parity Public License would be a suitable choice of public license. It's a strong copy-left license that requires licensees to open source the code they develop with the software. This means that developers of proprietary software would need to buy a private license. Parity hasn't been approved by the OSI due to their dysfunctional, inconsistent license review process, but it clearly fits the Open Source Definition. https://paritylicense.com/ For source-available licenses that don't fit the OSD, there are many options: * Polyform Small Business License https://polyformproject.org/licenses/small-business/1.0.0 * Polyform Non-Commercial License https://polyformproject.org/licenses/noncommercial/1.0.0 * Prosperity Public License https://prosperitylicense.com/ * strictEq Free License https://stricteq.com/free/1.1.0 All of the licences mentioned above are flipped forms. They are short and written in every day language, so don't hesitate to read them. https://flippedform.com/ Kyle Mitchell has been putting great effort into helping developers get paid for their work. See also strictEq and License…