Replies: 1 comment 1 reply
-
Thank you for asking me! I would like to explain why. We are using CouchDB as a remote database and using PouchDB as a local database. And both of them can synchronise with each other easily. As you said, CouchDB/PouchDB is not a popular database engine but also solves a big part of the difficulties of this plugin. Without this, Self-hosted LiveSync would not be made. Notable advantages are like below:
So we rely on them for half part of this plugin. Let me make an addition a bit more about the "open". If we made a new server-side software, it would have to be audited. (Especially the people who are required to be self-hosted inside their network would need so) Of course, other implementations are also always welcome. We are able to make an adapter for the PouchDB to connect to the backend of your choice. (This might be one of the values of being open too) If I received the pull request for the adapter which you made, I would love to configure that scheme as a connectable URI. (And this is why the remote-database configuration is not |
Beta Was this translation helpful? Give feedback.
-
A lot of people already have a website, which means they'll be paying per month or per year for shared hosting.
Is there a reason couchdb, in particular, was used?
There are a few others (lower performance) like:
SleekDB
NeDB
Which would run on shared hosting, but I'm unsure if they'd give the correct level of performance. I'd be interesting in helping to adopt if they'd work.
Beta Was this translation helpful? Give feedback.
All reactions