3 ms·

HTML5 - http://pouchdb.com http://pouchdb.com iOS, Android, .NET, Java - http://developer.couchbase.com/mobile http://developer.couchbase.com/mobile Hosted - ht

• marpalmin 12y ago
  This is exactly why I went for couchbase and decided to avoid firebase.
  • skrebbel 12y ago
    Assuming you use PouchDB, how do you avoid syncing the entire database with all users?
    • willholley 12y ago
      database-per-user is a common pattern with CouchDB. If you need to aggregate data across your users for reporting etc then you can use a server-side replication to create a "master" database which is only accessible to your internal users. You could also use filtered replication but it is: a) not scalable b) not secure (the whole db would still be accessible to all users) Couchbase has a different spin on this via "channels" though I'm not sure how it interoperates with PouchDB.
      • jchrisa 12y ago
        Couchbase Sync Gateway's channels are just slices through the data. The mechanism is internal to the Sync Gateway (you write a JS function that says who can see which channels and which channels a doc belongs to.) Replicating clients don't Need to know about this filtering, so channels work great with all flavors of Couch.