CouchOne, Membase Merge, Form NoSQL Powerhouse

Julie188 writes "CouchOne and Membase, two of the most popular noSQL projects, have merged in an attempt to become an open source database powerhouse. Even the company's new name is merged: Couchbase. The founders of the new Couchbase say they will offer the ability to scale from the largest data center and distributed cloud environments all the way down to smartphones and other mobile devices. As is the standard disclaimer during merger announcements, the leaders also promise to continue their support for their open source, community versions of their programs."

cool!

[larry bagina]

instead of two projects I've never heard of, I'll only have to ignore one!

Re:

[monkyyy]

exactly

Re:

[mini me]

If only [slashdot.org] Slashdot would [slashdot.org] have covered [slashdot.org] them before [slashdot.org]...

Re:cool!

[roaryk]

The initial post is misleading. The "two of the most popular noSQL projects" are in fact not CouchOne and Membase as it suggests. The fame should rather be attributed to CouchDB and Memcached, of which it would be rather hard indeed not to have heard. CouchDB has been developed by Damien Katz, the founder and CEO of CouchOne (created in order to commercialize the technology). Membase in turn is a NoSQL solution based upon Memcached (protocol-compatible).

Re:

[lehphyro]

Memcached is a distributed in-memory cache implementation, it has nothing to do with noSql. See: http://code.google.com/p/memcached/ [google.com]

Re:

[tomtomtom777]

Memcached is a distributed in-memory cache implementation, it has nothing to do with noSql. See: http://code.google.com/p/memcached/ [google.com]

Incorrect

Memcached is a key/value store, which doesn't use SQL or RDBMS concepts and is therefore by definition a noSql project.

The fact that is an in-memorty cache implementaion is irrelevant.

Re:

[lehphyro]

Did you read the project description on the link I provided? Here it is:

memcached is a high-performance, distributed memory object caching system

I didn't know caching system has been redefined to be nosql... Now java.util.HashMap is a nosql implementation!

Re:

[mini me]

Membase is the NoSQL database. The same people are responsible for Memcache, and thus it was part of this merger.

Re:

[tomtomtom777]

Memcached is a distributed in-memory cache implementation, it has nothing to do with noSql. See: http://code.google.com/p/memcached/ [google.com]

Incorrect

Memcached is a key/value store, which doesn't use SQL or RDBMS concepts and is therefore by definition a noSQL project.

The fact that it is an in-memory cache implementation is irrelevant.

Simple math

[Heliologue]

If my calculations are correct, the resulting product should be twice as good!

Re:

[Anonymous Coward]

If my calculations are correct, the resulting product should be twice as good!

2x0 is still 0

obligatory xtranormal video

[russlar]

whenever I hear nosql, I instantly think of this: mongodb is web scale: http://www.youtube.com/watch?v=b2F-DItXtZs [youtube.com]

Re:

[account_deleted]

Comment removed based on user account deletion

Re:

[eternalelegy]

Weird, whenever I hear nosql I instantly think about how much fun it will be to castrate my first bull, down on the farm.

obligatory xtranormal rant

[tepples]

Whenever I watch one of these xtranormal videos, the voices just don't match [tvtropes.org]. The characters look like the NPCs from Nintendo's Animal Crossing video games. So I come in expecting to hear higher-pitched Looney Tunes style voices, which match how I imagine the Animal Crossing NPCs speaking based on what the in-game "animalese" sounds like, and these voices sounding like grown men just strike me as jarring.

Re:

[bigstrat2003]

If /dev/null is fast and web scale, I will use it!

Re:

[Anonymous Coward]

I hate to so it but these kinds of products are not designed with your requirements in mind. I run a single application that can approach burst rates of over 200000 hits per second. Your acid compliant database would be flopping around like a dying fish at those transaction rates.

Re:

[mini me]

CouchDB, for one, is ACID compliant. NoSQL has nothing to do with lack of ACID compliance or performance. It is a catchall term to refer to a whole range of databases that are designed to solve different problems without using SQL as the query language.

Re:

[eternalelegy]

The article you linked is mostly an explanation of why Facebook switched from Cassandra to HBase, which they currently use.

Still a NoSQL product, just saying.

Re:

[icebraining]

Facebook (Cassandra)
Google [Maps,Earth,Gmail,Youtube,App Engine,Code,Reader,etc] (BigTable)
Zynga, Paypal, Vodafone (Membase)

Re:Fail ACID, fail in life...

[mini me]

Amazon (Dynamo)
Twitter, Digg (Cassandra)
Yahoo (HBase)
Netflix (SimpleDB)
BBC (CouchDB)

The Lotus Domino database is also NoSQL and is used in many enterprises.

Fuzzy wuzzy logic

[tepples]

Yeah, but then Facebook and half of Google are "fuzzy logic experiments" themselves.

Re:

[Hognoxious]

Google [Maps,Earth,Gmail,Youtube,App Engine,Code,Reader,etc] (BigTable)
Zynga, Paypal

Hmm, that probably explains a lot!

Re:Fail ACID, fail in life...

[snookums]

NoSQL doesn't mean unreliable, and SQL doesn't mean ACID-compliant.

CouchDB (one of the products mentioned in this article) goes to some lengths to preserve data integrity. It doesn't do delayed commits the way, say, MongoDB does, and it uses an append-only file format that means each document is written to disk in a completely ACID-compliant way.

MySQL didn't have any transactional capability in early versions, and even today is quite happy to corrupt tables beyond repair if the power goes out during a write operation.

Re:Fail ACID, fail in life...

[antifoidulus]

These tools don't "mangle" data in the sense you seem to think they do, quite simply what these tools do is provide an "eventually consistent" database. IE a write won't necessary be propagated instantaneously to every single database. Instead it will be "eventually"(with eventually depending on the scope of the problem and the overall system architectures involved) be consistent. Now for large classes of problems(social networks, search engines, message boards like /.), this is a huge boon. By relaxing the timeline constraint for consistency then can make both reads and writes MUCH faster, scale up better, handle faults better etc. However you are right in that there are also large classes of problems for which eventual consistency isn't a very useful tool. For instance a real time database in a factory or even databases for small businesses where there is no real benefit to going to an eventually consistent system with more fluid data structures. Again, right tool, right job.

Aggg! I never should have RTFA!

[Guidii]

And I got to enjoy this piece of wonderful writing:

"No matter how you slice it, I think this is merger is full of awesomesauce."

I'll never do that again..

Re:

[dingfelder]

awesomesauce ?

That is almost better than the bushism "misunderestimated"