Nitrite/Java: Storage Capacity and Production Suitability for Persistent Nitrite DB

[ela4490]

I’m exploring the use of Nitrite DB with persistent storage (MVStore/RocksDb) for a production scenario.

I couldn’t find specific details in the official documentation regarding storage limits or scalability. I wanted to confirm:

1. Is there any upper storage capacity limit when using Nitrite in persistent mode?
2. Would Nitrite be suitable for processing and storing metadata for over 30,000 documents per day?

It would be helpful to know if Nitrite has been benchmarked for similar workloads, or if there are any guidelines for production-scale deployments.

Thanks!

[anidotnet]

By design nitrite's storage capacity and production suitability is directly proportionate to it's underlying storage engine. So you should be looking into the guidelines related to the underlying storage engine for your workload. If your workload is suitable for MVStore you choose MVStore adapter, similarly if RocksDb suites more to your usecase you choose RocksDb adapter.

Generally if you want to use Nitrite for android, you need MVStore, if you are building for server, you go for RocksDb.