couchbase: All content tagged as couchbase in NoSQL databases and polyglot persistence
When I first read the OMGPOP story I wrote the Two Sides of the OMGPOP Cloud and Couchbase Scalability Story. Then came a long conversation with James Phillips of Couchbase. Now we have a better picture of Couchbase’s involvement in OMGPOP scaling success story:
We became aware of our role in their success when they called us to ensure they were employing best practices in planning for growth of their database cluster. As the number of users, games, and drawings grew at an unprecedented rate, they were able to continuously add capacity to the cluster (growing to over 100 servers), while maintaining application performance and with zero application downtime. There was never a performance drop or a single moment when new players couldn’t join the party – even in the face of dying hardware! At one point, a motherboard issue with their selected hardware was taking cluster members down at a frightening pace. Couchbase took even those failures in stride without interrupting game operation or performance.
For the future I hope Couchbase people will remember James Phillips’ promise. Time to moving on now.
Original title and link: Couchbase at OMGPOP: Some Clarifications ( ©myNoSQL)
When reading it, I’ve jotted down:
- The good: using a combination of cloud and a NoSQL database (Couchbase) allowed OMGPOP to scale
- The bad: OMGPOP had to call in people from Couchbase to help out with scaling
Question is if you can throw in more iron and hire experts wouldn’t many other database solutions be able to cope with OMGPOP’s growth?
Original title and link: Two Sides of the OMGPOP Cloud and Couchbase Scalability Story ( ©myNoSQL)
Very interesting visualization of some of the companies in the Big Data market connected through their venture capital and investment firms by Benedikt Koehler and Joerg Blumtritt over Beautiful Data blog:
There’s only one company I couldn’t find on this map: Hortonworks.
Original title and link: Big Data Investment Network Map ( ©myNoSQL)
Just in case you thought someone made up the whole thing about the status of CouchDB being confusing:
On the other hand I’m still trying to figure out if things in CouchDB land were more confusing than the various Hadoop versions out there. If you compare the two genealogy trees you’ll notice a reversed pattern.
Original title and link: History of Couch Projects ( ©myNoSQL)
Here are the 5 bullet points that would helped Couchbase clarify all the confusion about Couchbase, Membase, CouchDB:
- We are working on Couchbase server 2.0. This is our next major release and the only product we will be focusing next. It represents the continuation of our current Membase server product.
- Until Couchbase server 2.0 is out, we might release one or two updates to our Membase server that are addressing the most important issues.
- We will provide a migration path to users of Membase server to Couchbase server 2.0
- We will not support anymore our distribution of CouchDB known as Couchbase Single Server. Damien Katz, creator of CouchDB, has decided to step away from the Apache CouchDB project and focus on Couchbase development.
- Due to the major changes in Couchbase server 2.0, we will not offer a migration path for the users of Couchbase Single Server to Couchbase server 2.0.
Original title and link: Couchbase: Clarifying Confusions in 5 Bullet Points ( ©myNoSQL)
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)