Cloudant: All content tagged as Cloudant in NoSQL databases and polyglot persistence
From IBM to… IBM: The short, but complicated history of CouchDB, Cloudant, and a lot of other companies and projects
Damien Katz created CouchDB after working at IBM on Lotus Notes: CouchDB and Me. CouchDB went the Apache way. Then things got complicated…
On the West coast, Damien Katz and a team of committers created Couchio, later renamed to CouchOne, later merged with Membase to become Couchbase, which finally dropped CouchDB. Damien Katz left Couchbase.
East Coast, Cloudant took CouchDB and made it BigCouch. I thought that Cloudant will be the CouchDB company — and in a way it was. Cloudant put BigCouch on the cloud as a service and on GitHub as open source. BigCouch is supposed to get back into Apache CouchDB, but many months later this hasn’t materialized yet.
To complete the circle, today IBM announced signing an agreement to acquire Cloudant — news coverage on GigaOm, BostInno, TechCrunch. Which probably makes sense considering Cloudant’s relationship with SoftLayer and IBM’s $1 billion Platform-as-a-Service Investment, but less so if you consider the IBM and
Anyways, the future of Apache CouchDB is bright. Yep.
Original title and link: From IBM to… IBM: The short, but complicated history of CouchDB, Cloudant, and a lot of other companies and projects ( ©myNoSQL)
Cloudant says that during 2012, a year that saw its staff grow to 45 employees, the company’s customer base grew to more than 12,000 multi-tenant customers, counting both free customers, as well as the 50 that pay for its dedicated clusters.
I wholeheartedly hope these results are not indicative for the Database-as-a-Service market. I also wish Cloudant an even better 2013.
I haven’t seen any numbers from major platforms like Amazon Web Services, Heroku, or Rackspace, so if you have any please do share them.
Original title and link: The Business of Database as a Service ( ©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)
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)
Today, we are proud to introduce Iris Couch, a Couchbase spin-off and your new one-stop shop for hosted CouchDB. We are transferring the Couchbase hosting business to Iris Couch – a company founded and operated by the former Couchbase hosting team – and Iris Couch will focus solely on providing the rock-solid hosting service you deserve.
We know you’re wondering “What does this mean for me and my couches?” Relax. The name is changing, but the platform is not. Same platform. Same service. Same team. You don’t even need to touch your existing couches…the transition to Iris Couch will be seamless for you.
What is the value proposition or differentiator of Iris Couch (let’s say compared to Cloudant)?