3 ms·
Could you provide any links for using CouchDB in this kind of use case? I wasn't aware of it as a solution to this problem (but only as a document db) and woul
by jonahx 12y ago
Could you provide any links for using CouchDB in this kind of use case? I wasn't aware of it as a solution to this problem (but only as a document db) and would like to learn more.
- rakoo 12y agoCouchDB takes things a step further: instead of having all your data on a server and gradually sending changes to each interested party, CouchDB's way is to have a data store on each "node" (the server and all clients in a traditional web server model) and synchronize data (ie documents), possibly continuously. Then on the clients you react to changes and update the UI. Your application only manages the data locally, and the CouchDB components manages everything network-related. To do it, one useful component is PouchDB (http://pouchdb.com/ http://pouchdb.com/), which is a data store in the browser. You just hook it to whatever backend you want and access the data with a straightforward javascript API. There's also the much larger (in scope) Hoo.ie, but I can't talk much about it... Unfortunately I don't have any links for you, I'm looking for experiences just like you ...
- JoeAltmaier 12y agoIs CouchDB still a thing? I thought it didn't scale past 6 instances or some such. And scaling was the whole point.