2017-04-11 10:45 GMT+02:00 Simon Temple <[email protected]>: > > The database I wish to replicate contains user information. This information > is not updated very frequently but is read often. <http://bit.ly/1Lqt8qy> >
We use a simple nodejs script to manage replications in a similar (I guess) case, it's build around follow and nano. We do follow DB changes, when a database changes a continuous replication for this DB is started and canceled again after a timeout. A change to a db while the replication is running resets the timeout. The replicated sequences are captured, so next time a replication is started it is started with the correct "since" parameter. This way, though each user got his own database, we keep the concurrent running replications pretty low. -- Stefan
