Before we get back to our regularly scheduled programming..
Having worked with Apache CouchDB for quite some time, and with BigCouch more recently with the 2600hz platform, it was odd, to say the least, to read Damien’s blog post concerning his exit from the CouchDB project.
While moving on to greener pastures is a common occurrence, and no one expected Damien to stay with the project for the rest of his life, framing the project he’s leaving in a negative way and highlighting the positives of his new, competing project, is disingenuous at best and definitely saddening. A lot of smart engineers and users have spent time working on the CouchDB project, and to dismiss the project so callously is a disservice to the community’s efforts.
Regardless, we wanted to make sure we let our community know that, despite the theatrics and general brouhaha that can follow announcements like this, our path remains unchanged in respect to our choice of datastore.
BigCouch leverages CouchDB for its storage on disk, and provides management, clustering, internal replication, sharding, and more, on top of that code base. They are a mature company focused on making BigCouch more stable, and more feature-rich, as any worthwhile company does with their flagship product.
We leverage BigCouch in part because of our confidence in Cloudant’s ability to continue to enrich their platform (and by extension, Apache CouchDB). They are a smart bunch of engineers and we value their contribution to making our platform as fault-tolerant as possible. Their vision gels nicely with ours: big data served reliably across a redundant cluster of machines.
If you’re new to the ideas of CouchDB and BigCouch, and wondering why a telephony company like us uses BigCouch, listen to Darren in this webinar as he gives the history of the decision and the experience thus far working with and administering BigCouch in production.
Life is good. Now back to your regularly scheduled programming.
Posted by James Aimonetti, Distributed Systems Engineer