CouchDB + PouchDB

BiBo · June 16, 2021, 9:53pm

Hello, in this thread I invite you to discuss the bundle:
As Server-side Component and Database Manager connector - https://couchdb.apache.org/
And as Local Storage - https://pouchdb.com/

I understand that there are a lot of NoSQL databases (I think more than users wappler).
Main idea thanks to kinship these two databases, you can get a single interface and logic for working in Wappler both on the server side and on the client.
Hypothetically, in Wappler we no need use Views concept a lot of this is already done by Wappler with JSON data.
I understand that this is probably naive, and this leaves replication, versioning and synchronization, and in general, real web development masters do not need this in Wappler?

For database manager editor add JSONGrid or like JSON Editor: JSON Grid View in XMLSpy
https://www.youtube.com/watch?v=ZTt-_Te9a9c
As Fauxton alternative.

JonL · June 17, 2021, 7:55am

So far I haven’t had the need to use these two databases in my projects as I don’t develop for mobile with Wappler.

Maybe someone that has use them externally and interfaced with them can chip in.

sitestreet · June 17, 2021, 8:26am

I have a mobile project which I’ve had to put on hold because one of the key features is offline sync so I’m mega keen for some kind of implementation on this and PouchDB seems to be the one to go with.

s.alpaslan · June 17, 2021, 9:56am

yes @BiBo
PouchDB and CouchDB are really good but it would be useful to examine realm db as well.

BiBo · June 17, 2021, 10:05am

This is what I was afraid of, their legion CouchBase, MongoDB etc.
I understand that CouchDB and PouchDB are not a panacea, but there are no perfect solutions.
For example, instead of CouchDB, you can use the PouchDB server, it is modular, and run one database as storage on the server, the second database as local storage on the client and the third inmemory database, and use it for search and caching on the client and connect replication between them.