ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

couchdb: All content tagged as couchdb in NoSQL databases and polyglot persistence

Jelastic Database Marketshare: MySQL, MongoDB, MariaDB

Jelastic, a company offering a cloud platform for Java server hosting, has published some stats about the databases used by their over 7000 users:

Jelastic Database Marketshare

While it would be wrong to generalize these results to absolute database marketshare, it is interesting nonetheless to see that MongoDB is already outrunning PostrgeSQL being the second most used database and that CouchDB, which was added only one month ago, is already used by 5% of Jelastic’s users. MySQL detains the first position with over 40% users or differently put double the number of the second place (MongoDB).

These numbers would be even more interesting if they would account for some real usage stats like database sizes or query volumes.

Mat Keep

Original title and link: Jelastic Database Marketshare: MySQL, MongoDB, MariaDB (NoSQL database©myNoSQL)

via: http://blog.jelastic.com/2012/01/23/database-marketshare-january-2012/


Couchbase: Clarifying Confusions in 5 Bullet Points

Here are the 5 bullet points that would helped Couchbase clarify all the confusion about Couchbase, Membase, CouchDB:

  1. 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.
  2. 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.
  3. We will provide a migration path to users of Membase server to Couchbase server 2.0
  4. 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.
  5. 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 (NoSQL database©myNoSQL)


CouchDB: A Season Finale

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.

While I could understand some of the criticisms[1], my conclusion was pretty close to what Bradley Holt wrote:

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 (NoSQL database©myNoSQL)


Interesting Data Sets and Tools: Monthly Twitter Activity for All Members of the U.S. Congress

Drew Conway:

Today I am pleased to announce that we have worked out most of the bugs, and now have a reliable data set upon which to build. Better still, we are ready to share. Unlike our old system, the data now lives on a live CouchDB database, and can be queried for specific research tasks. We have combined all of the data available from Twitter’s search API with the information on each member from Sunlight Foundation’s Congressional API. […] But be forewarned, working with this system and CouchDB requires a mature understanding of several tools and languages; including but not restricted to; curl, map/reduce, Javascript, and JSON. And that’s before you have even done any analysis.

Original title and link: Interesting Data Sets and Tools: Monthly Twitter Activity for All Members of the U.S. Congress (NoSQL database©myNoSQL)

via: http://www.drewconway.com/zia/?p=2846


TouchDB: Embeddable Lightweight CouchDB-compatible

Jens Alfke:

If CouchDB is MySQL, then TouchDB is SQLite.

By “CouchDB-compatible” I mean that it can replicate with CouchDB and Couchbase Server, and that its data model and high-level design are “Couch-like” enough to make it familiar to CouchDB/Couchbase developers. Its API will not be identical and it may not support some CouchDB features (like user accounts) that aren’t useful in mobile apps. Its implementation is not based on CouchDB’s (it’s not even written in Erlang.) It does support replication to and from CouchDB.

In my books a perfect solution must:

  1. be small
  2. be fast
  3. reuse the target platform technologies (so it feels at home)
  4. support bi-directional synchronization with CouchDB
  5. provide an API that is either similar to the target platform APIs or is similar to CouchDB API

Data story

Original title and link: TouchDB: Embeddable Lightweight CouchDB-compatible (NoSQL database©myNoSQL)

via: https://github.com/couchbaselabs/TouchDB-iOS


Couchbase Server 2.0 Durability and Write Performance

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 (NoSQL database©myNoSQL)


CouchDB's File Format Is Brilliantly Simple and Speed-Efficient at the Cost of Disk Space

Riyad Kalla:

I have been reading up on log structured file systems, efficient data formats, database storage engines and copy-on-write semantics for a little more than week now… reading about the pros and cons of different approaches and seeing it all come together so smoothly in a single design like Couch’s really deserves a hat-tip to the Couch team.

Great post looking at the pros of CouchDB storage format and the tradeoffs the team made on the way.

Original title and link: CouchDB’s File Format Is Brilliantly Simple and Speed-Efficient at the Cost of Disk Space (NoSQL database©myNoSQL)

via: https://plus.google.com/u/0/107397941677313236670/posts/CyvwRcvh4vv


Will Cloudant Become the CouchDB Go to Company?

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? (NoSQL database©myNoSQL)


Document Databases and Data Migrations

Sven Schmidt:

Since CouchDb is inherently unstructured, there’s no global schema that you manage to control your data’s structure. That’s often a good thing, because it gives you flexibility, but it can also cause problems, for example when you want to access documents without handling against all sorts of different “versions” of your document you might have.

When we first talked about document databases we said:

  1. no more ORM. Do a search or take a quick look at this list of NoSQL libraries and see if that still stands.
  2. no more schema constraints. The moment the structure of the data showed signs of evolving too rapidly, we started to look for ways to test document structure for inconsistency
  3. no more data migrations. Maybe no data migrations, but data versioning might be needed long term.

I think I’ve already written this once, but here it is again: the sum of constraints in a system is constant. The more relaxed the rules are on a component, the more constraints the rest of the components will need to support.

Original title and link: Document Databases and Data Migrations (NoSQL database©myNoSQL)

via: http://catbrainblog.wordpress.com/2011/12/19/couchdb-migrations/


Unintentional Market Confusion... Membase, CouchDB, or Couchbase

Not everything went as we hoped or expected, however. Unfortunately, we confused the heck out of many of our potential users. In addition to Membase Server and our new mobile products we also offered Couchbase Single Server which was a packaged “distribution” of Apache CouchDB. On top of that we began releasing developer previews of Couchbase Server 2.0, which incorporated CouchDB technology into Membase Server – but this product was not compatible with Couchbase Single Server (or CouchDB). If you are confused just reading this you get the point – and so do we.

Finally.

Original title and link: Unintentional Market Confusion… Membase, CouchDB, or Couchbase (NoSQL database©myNoSQL)

via: http://blog.couchbase.com/couchbase-2011-year-review


Why I Choose CouchDB Over MongoDB

Theres a lot of discussion lately over NoSQL databases for high-performance distributed web apps. […] Currently there are 2 main contenders; CouchDB and MongoDB, and if you care about your data saving, and alway having your data available MongoDB is not a good fit.

FUD

Original title and link: Why I Choose CouchDB Over MongoDB (NoSQL database©myNoSQL)

via: http://www.chrisallnutt.com/2011/12/08/why-i-choose-couchdb-over-mongodb/


11 Document-Oriented Databases Which Are 8: CouchDB, Jackrabbit, MongoDB, RavenDB

Such list would be even more useful with the following classification:

Production ready

Experimental

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.

Abandonware

Original title and link: 11 Document-Oriented Databases Which Are 8: CouchDB, Jackrabbit, MongoDB, RavenDB (NoSQL database©myNoSQL)