4 ms·
I can't see how this could for a readonly database, but how would you resolve collisions on writes and don't make them super slow in the process?
by eterevsky 3y ago
I can't see how this could for a readonly database, but how would you resolve collisions on writes and don't make them super slow in the process?
- antonvs 3y agoRight, it certainly wouldn’t work for a big multi-tenant db. But the right data organization can make it work. In our case, the data is organized such that there’s usually only one client at a time that would need to write to a given db file. Think for example of a folder per user, each containing a db file and various other files for that user. What we’re doing is actually even more granular than that - we have a folder for each object that a user could be working on at a given time.