CouchDB: All content tagged as CouchDB in NoSQL databases and polyglot persistence
There was a story earlier this year that I, as someone that has spent an enormous amount of time contributing to open source projects, thought it was no story. Considering how much was published about it, chances were you already read something about Damien Katz’s The future of CouchDB.
At the time of that post, my draft looked like this:
And now I, and the Couchbase team, are mostly moving on. It’s not that we think CouchDB isn’t awesome. It’s that we are creating the successor to it: Couchbase Server. A product and project with similar capabilities and goals, but more faster, more scalable, more customer and developer focused. And definitely not part of Apache.
Elvis has left the building. Please welcome The Beatles!
I always thought that some sort of a message from the its creator was needed to completely clear the waters about CouchDB. Damien’s post together with the earlier post from Couchbase announcing the discontinuation of the Couchbase Single Server (Couchbase’s CouchDB distribution) were bringing closure to the CouchDB saga. And that was good.
I knew that the Apache CouchDB project and community are doing fine. Noah Slater’s email just confirmed that:
As some of you may have already read, Damien Katz, Apache CouchDB’s original developer, has publicly announced that he intends to focus his time exclusively on developing other products for his company. Damien has had very little involvement in the CouchDB project for a year or more now, so, for many people, this is confirmation of what they already knew. […]
Our biggest strength has always been the breadth and depth of our community of developers and users. In the very near future, we’ll be voting in a new committer, appointing a new PMC member, sprucing up the website, and making a major new release
Late last year, I also suggested that Cloudant would become the go to company for CouchDB. Adam Kocoloski’s post confirmed this too:
We, along with a host of other companies, strongly support the open source community in building CouchDB and we do not plan on stopping. We have been fortunate in our ability to attract outstanding engineers, investors, and customers. We intend to continue devoting resources to Apache CouchDB and offer our help in any way the community desires.
Going forward, you’ll have two choices, either Apache CouchDB or Couchbase Server. The road map for Apache CouchDB will continue to be determined by community consensus. The road map for Couchbase Server will be determined by Couchbase, the company.
But I was left with a nagging feeling that I missed something. I kept on circling around a small part of the original post:
What’s the future of CouchDB? It’s Couchbase.
How could a product that is removing defining features (e.g. the HTTP RESTful API or the peer-to-peer replication), that is already different (Volker Mische’s post provides details), and that offers no clear migration path be the future of CouchDB?
The answer is actually simpler than I thought:
Couchbase is the future of CouchDB as CouchDB was the future of Lotus Notes. A new product that takes inspiration from the experience and lessons learned while building the previous one.
And that was a CouchDB season finale. I’m already looking forward to the next season’s plots.
Original title and link: CouchDB: A Season Finale ( ©myNoSQL)
Matt Ingenthron in a forum thread:
There is quite a bit of work ongoing to optimize some of these paths, and there are some features coming to allow you to specify that you want to block until a change is durable at either the replication or the disk IO level. I believe use that internally to the server for prioritization as well.
Right now we write things as fast as we can and we constantly scan.
I think I’ve seen this before. And I thought Couchbase Server 2.0 will be using CouchDB durable persistence engine. Couchbase Server 2.0 is still in developer preview so there’s time for this to change. But some clarifications would be welcome.
Original title and link: Couchbase Server 2.0 Durability and Write Performance ( ©myNoSQL)
I read that:
- Cloudant might have raised $2.1 million (via Mass High Tech)
- Cloudant has a new CEO in Derek Schoettle (previously VP Sales at Vertica Systems, Inc.) (via PR announcement)
After Membase and CouchOne merger, I think it was the general expectation that the new formed Couchbase will carry on CouchOne promise of being the commercial supporters and service company for CouchDB. This made sense considering Couchbase has been offering a CouchDB product: Couchbase Single Server.
On the other hand this situation created a lot of confusion in the CouchDB world and Couchbase offering. It was only one week ago that Couchbase finally came out to clear the waters: they are not and won’t be a support company for CouchDB , nor will they continue offering a CouchDB-only product.
So there’s an unfilled spot in the NoSQL world: a go to company when CouchDB services and support are needed. Truth is I don’t have enough data to decide if there’s also a need in the market for it though.
But I’m wondering if Cloudant will pursue this positioning. At least that’s how I read Cloudant ex-CEO Alan Hoffman words. Or will the change of CEO also mark a change of direction?
Original title and link: Will Cloudant Become the CouchDB Go to Company? ( ©myNoSQL)
Such list would be even more useful with the following classification:
Note: A special mention in this category for OrientDB and Terrastore which even if they might not be largely adopted they are still active projects probably counting a couple of production deployments.
Original title and link: 11 Document-Oriented Databases Which Are 8: CouchDB, Jackrabbit, MongoDB, RavenDB ( ©myNoSQL)