Migrating from CouchDB to ... ??

-
There is a thread/vote on LinkedIn asking "Would you consider migrating to couchbase from couchdb"
Which would be a useful and relevant data point if you thought of it as "Would you consider migrating to couchbase from another NoSQL store, e.g. couchdb (or mongoDB, Riak, etc.)"
However, given the way the question was phrased the thread pretty rapidly devolved to the usual CouchDB vs CouchBase discussion.

And that is is a bit of a trick question - CouchDB and CouchBase are different products (bear with me here).  As I allude to here  the NoSQL space is a "solution-oriented" space.  The point is that unlike the SQL space, where you can pretty much use MySQL / PostgreSQL / Oracle / whatever for *any* of your problems (money willing), in a NoSQL environment it is different.  If you've done your homework, you'll have picked the appropriate NoSQL store for your application right off the bat.  If you haven't, well, you'll probably end up switching to something else, a-la Signal.

CouchDB has a sweet-spot - and works brilliantly there.  The logical successor for CouchDB is bigcouch - which addresses back-end sharding/scaling for CouchDB brilliantly.  It is also getting rolled into CouchDB anyhow (per Cloudant). 

CouchBase is *different*.
Not better (though maybe it is).
Not *worse* (though maybe it is).
*Different*.

It has its own sweet spot.  Talking about migrating from CouchDB to CouchBase is akin to asking if people are going to migrate from CouchDB to Riak, or MongoDB, or whatever.
Could you migrate? Sure. 
Should you?  Depends.
I'd say it really, really depends on what your application does.  But it is *not* axiomatic that the migration path from CouchDB is to CouchBase.  For today at least, the migration path for CouchDB is CouchDB.
 

Comments

Post a Comment

Popular posts from this blog

Erlang, Binaries, and Garbage Collection (Sigh)

-
Image
The nice thing about garbage-collection is that it is makes memory management absolutely transparent to you Of course, the above is true right up to the point when it stops being transparent, at which point it does a phase change from nice to clusterf**k of biblical proportions .  There are entire posts, books, and suicide notes that have been written about this, and I have no great desire to add to them, save with the minor comment that paranoia about garbage-collection is still justified , albeit only in the edge-cases for most people. That said, I'll give you that Erlang GC is in many ways much, much better positioned in this regard than, oh, Java, but it still rears up and bites you in the butt when you least expect it. ( More information about Erlang's GC vis-a-vis Java here , and Jesper's truly excellent description of Erlang's GC here ).  A story from the past should serve to illustrate this. Once upon a time, in a magical land far far away - well, Her
Read more

Visualizing Prime Numbers

-
Image
From Jason Davies , we have El Patron de Los Primos , probably one of the coolest prime number visualizer that I've seen.  For every Natural number, he draws a periodic curve that intersects at that number and each of its multiples.  Needless to say, prime numbers are touched by only two curves (itself and 1 ). You can scroll to the right, and move up the prime food change. (The image above is a screen grab.  Go here to see the actual thing)
Read more

Its time to call Bullshit on "Technical Debt"

-
Image
Seriously. You know what " Technical Debt " is, right? Ok, heres the (official?) Wikipedia definition   Technical debt   (also known as   design debt   or   code debt ) is a   neologistic   metaphor referring to the eventual consequences of poor or evolving   software architecture   and   software development   within a   codebase . The debt can be thought of as work that needs to be done before a particular job can be considered complete. As a change is started on a codebase, there is often the need to make other coordinated changes at the same time in other parts of the codebase or documentation. The other required, but uncompleted changes, are considered debt that must be paid at some point in the future. And in this - somewhat purist - sense, " Technical Debt " is absolutely valid. The problem arises in the way it is almost invariably used, viz., as an excuse to not do something. Herewith a simple exercise - the next time you hear someone cite &quo
Read more