Hello!
Thanks a lot for this update and overview of the situation. As users (our
company has been using couchdb since 2015 circa as the main database of our 3
tier web apps), I feel it may be preferable to move the couchdb-fdb work to a
separate project having a different name. As Janh has ment
Hi there,
We have received your request #1692199 and we'll start working on it as soon as
possible. We usually respond within 24 hours, but please keep in mind that
there may be a delay in response over the weekend. In the meantime, check our
Help Center at https://support.ecwid.com/hc/en-us
Thank you for this feedback.
I think it’s reasonable to worry about tying CouchDB to FoundationDB for some
of the reasons you mentioned, but not all of them. We did worry, at the start,
at the lack of a governance policy around FoundationDB; something that would
help ensure the project is not b
As a user, my team and I were keenly looking forward to CouchDB v4 with
FoundationDB.
Given the current situation, it is only reasonable to come up with a
best alternative.
How about refactoring CouchDB to work with multiple storage engines?
The default CouchDB will support whatever the PMC
