| > in production. I went looking, but found nothing regarding any operations management. * How does this scale? * How is it monitored? Where do I get the metrics for it? (indexing performance, search performance, etc.. Stuff not found in the OS) * Are there any kind of throttling or queueing capabilities? * What's the redundancy/HA approach? * I'll ask about backups, though its the least of my worries as indexing databases like this and ES should be able to be rehydrated from source. However, snapshots may be faster to restore than reindexing. This might be a nice local dev tool for something, but I'm not sure how you run a business critical application with it? I'm wondering if I'm missing something. Edit: formatting Edit2: also wondering about security too |
* 2 parts.
- Vertical scale: We use LMDB as a key-value store. This one uses the power of memory mapping. It made our search engine use mainly the disk and will do not need a machine that will have TB of RAM.
- Horizontal scale. We are working on sharding and replications (Raft). Development is progressing well, and the functionality should come out soon.
* Currently, it is not monitored at all. This feature is planned. https://github.com/meilisearch/MeiliSearch/issues/523
* We use a queue for updates. You can find here the complete guide https://docs.meilisearch.com/guides/advanced_guides/asynchro...
* As I said previously, we are working on HA with a raft consensus.
* We will add snapshots in no time (disk folder saved in s3). A little more time for backups (version agnostic, need indexing).
We are already working with Louis Vuitton on an application in production. The app is in production from 9 months, and there hasn't been a single problem.