About 12+ years ago, i "invented" similar RPC-over-couchDB architecture as there wasn't much other distributed ways.
Worked wonders - each user reading/posting requests/responses in own "channel", the channel being replicated to server and any of user's devices, central server responding to requests and eventually cross-polinating the channels if need be.
Did a web client (pouchDB), android (touchDB), ios (forgot the name).. essentially each platform has its own implementation of the relatively simple protocol of Couchdb. So all one does is listen/read/write to a single local db.. and then db is doing all the communication, whenever possible. Simplified the clients sooooo much - reduced work and complexity like 50%.
Eh, the thing didn't go anywhere as product but nevermind :/
Worked wonders - each user reading/posting requests/responses in own "channel", the channel being replicated to server and any of user's devices, central server responding to requests and eventually cross-polinating the channels if need be.
Did a web client (pouchDB), android (touchDB), ios (forgot the name).. essentially each platform has its own implementation of the relatively simple protocol of Couchdb. So all one does is listen/read/write to a single local db.. and then db is doing all the communication, whenever possible. Simplified the clients sooooo much - reduced work and complexity like 50%.
Eh, the thing didn't go anywhere as product but nevermind :/
have fun