my current, newbie strategy, is to have multiple databases per user each dedicated to a single feature, like customizations of the look of a page, or the blog entries. this has the advantage of easy permissions enforcement, but the disadvantage of a worse than exponential explosion of the number of databases as features requiring a new database per user/role, and the number of users, grows.
and quite frankly i'm a bit afraid to just start designing something on my own, knowing next to nothing about the nitty gritty of replication in the real world. or should i just not be worried about 20 million databases per 1 million users? there is that b-tree feature which i assume is used for table-name to table data access too? On Fri, Oct 26, 2018 at 7:19 AM Rene Veerman <[email protected]> wrote: > Now that i've got blogging powered by couchdb and some other stuff powered > by couchdb done for my seductiveapps.com platform, > > i'm looking to start on email and chat features, between couchdb users and > even between roles or between a user and someone from a role. > > a role like 'law enforcement', because new anti-terror laws here require > that i build in a backdoor to any system that exposes blogging features to > the world. > > plus, i need reliable scalable email and chat features anyways for the > more advanced future features of my cms (webshop, forum, etc). > > so, i'm looking for smart db design ideas (i use php-couchdb and pouchdb), > and if any library to do this exists that's free to use commercially, i'd > love to hear about that too. >
