Slashdot Mirror

← Back to Stories (view on slashdot.org)

CouchOne, Membase Merge, Form NoSQL Powerhouse

Posted by Roblimo on from the one-big-base-instead-of-two-small-ones dept.

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."

4 of 46 comments (clear)

  1. cool! by larry+bagina · · Score: 5, Insightful

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

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

    1. Re:cool! by roaryk · · Score: 4, Informative

      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).

  2. Re:Fail ACID, fail in life... by snookums · · Score: 4, Informative

    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.

    --
    Be careful. People in masks cannot be trusted.
  3. Re:Fail ACID, fail in life... by antifoidulus · · Score: 4, Interesting

    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.

    --
    Monstar L