Forgot your password?
typodupeerror
Databases

Cassandra NoSQL Database 1.2 Released 55

Posted by Soulskill
from the onward-and-upward dept.
Billly Gates writes "The Apache Foundation released version 1.2 of Cassandra today which is becoming quite popular for those wanting more performance than a traditional RDBMS. You can grab a copy from this list of mirrors. This release includes virtual nodes for backup and recovery. Another added feature is 'atomic batches,' where patches can be reapplied if one of them fails. They've also added support for integrating into Hadoop. Although Cassandra does not directly support MapReduce, it can more easily integrate with other NoSQL databases that use it with this release."
This discussion has been archived. No new comments can be posted.

Cassandra NoSQL Database 1.2 Released

Comments Filter:
  • Re:Hmm. (Score:3, Insightful)

    by Anonymous Coward on Wednesday January 02, 2013 @05:20PM (#42454267)

    When the project is run by an idiot who thinks he needs to incorporate buzzwords over substance into their work.

  • Re:Hmm. (Score:5, Insightful)

    by Sarten-X (1102295) on Wednesday January 02, 2013 @05:27PM (#42454345) Homepage

    Assuming you're not trolling...

    When one wants to write a ton of data as fast as possible, where the data may not actually be complete or consistent (but still useful). Something on the order of a million rows a minute is a prime candidate for a NoSQL store. Consider, for example, the sum of all posts on Facebook at any given time.

    From the other side, an application like the current trend of "Big Data" models, monitoring every aspect of every action on a website (or in a hospital, or through a retail distribution chain, or the environmental systems of a factory) to glean statistically-meaningful information also makes a good use case for NoSQL. At the expense of consistency, the store is designed to be fast and fault-tolerant, so it really doesn't matter whether the data's complete or not. For Big Data applications, which are interested only in statistics, having a few inconsistent records out of billions doesn't matter much to the end result.

    Sure, traditional RDBMSs can be tweaked and optimized to make any particular query run as fast as any NoSQL engine... but that's an expensive and time-consuming process that's often not feasible.

"Gotcha, you snot-necked weenies!" -- Post Bros. Comics

Working...