Re: Architecture of a messaging app using Couchdb

You should be able to use a single on_change rule for all the DBs if you give the DBs a name that can be parsed, eg user_ as you can use a regex in the on_change rule. Spiegel will automatically take care of creating change_listener docs to keep track of the place in the _changes feed. You can comp

Re: Architecture of a messaging app using Couchdb

That should work, I think. But do Spiegel change listeners required for all the databases to achieve this? Anyway, I am going to try all the solutions discussed in the last post and this one to get a better understanding. Regards Sachin On Tue, Nov 28, 2017 at 8:53 PM, Geoffrey Cox wrote: > Th

Re: Architecture of a messaging app using Couchdb

On Tue, Nov 28, 2017 at 8:30 PM, Geoffrey Cox wrote: > Hi Sachin, > > I work on a teaching app called Quizster that handles some of the same > concerns. Here is my 2 cents: > > Quizster: wow, that's one awesome idea. On Tue, Nov 28, 2017 at 6:37 AM Sachin Divekar wrote: > > > Hi, > > > > I have

Re: Architecture of a messaging app using Couchdb

There is also a variation on 3. (the custom API) where you do use PouchDB. You could have users write messages to their database and then use Spiegel with an on_change rule that responds to new/edited messages and then copies tho

Re: Architecture of a messaging app using Couchdb

Hi Sachin, I work on a teaching app called Quizster that handles some of the same concerns. Here is my 2 cents: On Tue, Nov 28, 2017 at 6:37 AM Sachin Divekar wrote: > Hi, > > I have been studying a possibility to use Couchdb for a realtime messaging > app. The architecture I am thinking about

Architecture of a messaging app using Couchdb

Hi, I have been studying a possibility to use Couchdb for a realtime messaging app. The architecture I am thinking about is as follows. The app will access only the local offline database using Pouchdb which is in continuous replication with a remote Couchdb cluster. On the server, it'd be one dat