4 ms·
I'm currently working on an offline-first app with PouchDB as the data store on the front-end, and I'm going to use exactly this concept on the server. Each use
by emilecantin 7y ago
I'm currently working on an offline-first app with PouchDB as the data store on the front-end, and I'm going to use exactly this concept on the server. Each user will be an actual CouchDB user, with their own databases.
My use-case lends itself well to this paradigm, though. Other apps might not be able to to this as well as mine.
- AgentME 7y agoThe article describes a way to use one database for all users, and mentions cases like "each user can see all posts, but can only see the author field on posts they made". The difference between that and a database-per-user design is that in a database-per-user design, there's no shared data (or if there is, it's manually synced in to all of the databases by something outside of the database).
- emilecantin 7y agoYeah, that's exactly my use-case; there's very little shared data. I guess we'll have to wait for other use-cases!