Nick or Jens, any further thoughts for minimizing channel overload? I am trying to architect a similar design where users might share documents as individuals and teams. The major stumbling block is that there will be many sub-documents that will be continuously generated which may impact channel performance.
Solution 1: document (channel-doc-id) sub-document (channel-doc-id) user subscribes to many channel-doc-id channels (possibly too many channels per user) Solution 2: document ([channel-user-id, ...]) sub-document ([channe-user-id, ...]) (becomes prohibitive when there are changes in parent document channels) users would only have to subscribe to one channel per user Any thoughts? Thanks in advance On Wednesday, October 16, 2013 5:12:50 PM UTC-7, Nick Wood wrote: > > Looks like we have two options: > > 1. Manage a "channels" property for every document and update children > whenever a parent changes (triggering a re-sync for all of the other > channels, even though the meat of the document didn't change). > > 2. Continue to use CouchDB with a separate database per user like we've > been doing, which is a little more resource intensive, but a better > experience for the end users. > > Are there any other reasonable solutions that I'm not seeing? > > Nick > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/6d051789-7d4a-4440-8634-30eacaa634dc%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
