So we have a use case where we need to push certain JSON to a large number of users 100s of thousands and potentially can be in millions.
So we can have channels may be in 100s and those users can subscribe to those channels, but then we would be in a situation to subscribe/unsubscribe to those channels which you mentioned is an expensive operations. So out of following two , which one is a better design for this kind of use case.
1. Create channels may be in 100s or even in thousands, and then subscribe those users to specific channels ,and then JSON docs can belong to those channels, but JSON would only be associated with a ten of channels, which is fine I think , but then we would have issue to subscribing and un subscribing the user from those channels, which you mentioned is an expensive operation, how to handle this situation here ?
Also is there any limit in how many user can subscribe to a channel
2. We create one channels for each user so we have Millions of channels , one for each user. Now in this case each JSON would need to be associated with Millions of channels, is there any limit on how many Channel a JSON doc can belongs to ?
Also a question , since I am not very familiar with what kind of User are being talked about when Sync gateway docs refer to a users, are those App users, of a Custom App maintained users ?
Thanks