Optimal storage usage


We have group usage pattern that requires metadata update. It is possible that multiple simultanous updates can happen at the same time, and because of lack of any locking mechanism this may lead to data loss. To avoid this problem we plan to use built-in storage that supports optimistic locks. Is this ok from scalability and performance perspective (we are using Heroic Cloud) to have a collection with hundreds of thousands keys?

Hello @jlisicki-ccgames, the storage engine was designed to work at scale, the usage of optimistic locks allows you to prevent data loss with concurrent writes by using the version to ensure an update to the data has “seen” the most recent version of it and disallowing to update otherwise.

A collection with hundreds of thousands keys is perfectly fine.

1 Like