Hi, My team has been using CouchDB in different projects to support synchronization in mobile apps. We don't use a db-per-user pattern strictly but something that comes pretty close.
So far we have not encountered the limits and we are comfortable with CouchDB 3.x., we were not particularly interested in incorporating FoundationDB as we intuited a significant increase in the complexity of the architecture which, at least in our case, was not necessary (admittedly in exchange for very interesting functionalities). We prefer to refocus development on CouchDB 3.x, we do not have a clear position on the CouchDB-FDB option but would be concerned about any option that would result in dividing the project efforts. We believe that CouchDB 3.x has a lot of room for development with features that can help increase its adoption and improve its usage at least in our context: - Incorporate support for mobile sync clients, e.g. allow initial syncs without deletes. - Rethink the db-per-user pattern, perhaps as an idea partitioned _changes streams could help improve this aspect. - Allow permanent document deletions or something like expiration policies for deleted content. Any functionality that helps to keep databases compact. - Perhaps, better support for conflict resolution Thanks, Juanjo El jue, 10 mar 2022 a las 17:24, Robert Newson (<rnew...@apache.org>) escribió: > Hi, > > For those that are following closely, and particularly those that build or > use CouchDB from our git repo, you'll be aware that CouchDB embarked on an > attempt to build a next-generation version of CouchDB using the > FoundationDB database engine as its new base. > > The principal sponsors of this work, the Cloudant team at IBM, have > informed us that, unfortunately, they will not be continuing to fund the > development of this version and are refocusing their efforts on CouchDB 3.x. > > Cloudant developers will continue to contribute as they always have done > and the CouchDB PMC thanks them for their efforts. > > As the Project Management Committee for the CouchDB project, we are now > asking the developer community how we’d like to proceed in light of this > new information. > > Regards, > Robert Newson > Apache CouchDB PMC > >
