Free Newsletters:
DatabaseDaily  
Database Journal
Search Database Journal:
 
MS SQL Oracle DB2 Access MySQL PostgreSQL Sybase PHP SQL Etc SQL Scripts & Samples Links Database Forum

» Database Journal Home
» Database Articles
» Database Tutorials
MS SQL
Oracle
DB2
MS Access
MySQL
» RESOURCES
Database Tools
SQL Scripts & Samples
Links
» Database Forum
» DBA Jobs
» Sitemap

News Via RSS Feed


follow us on Twitter





New Security Features Planned for Firefox 4

Another Laptop Theft Exposes 21K Patients' Data

Oracle Hits to Road to Pitch Data Center Plans
Database Journal |DBA Support |SQLCourse |SQLCourse2









Systems Programmer / Software Engineer - C, Unix-Linux, Multi-threading, IPC
WSI Nationwide, Inc.
US-NY-New York

Justtechjobs.com Post A Job | Post A Resume

Mar 12, 2010

Digg is Switching to Cassandra

By DatabaseJournal.com Staff

Digg, the San Francisco-based social media company, is choosing Cassandra over MySQL saying that they plan to open source all of their work on Cassandra. Digg's system needs to support allot of interaction with their 40 million uses a month, so they need something that can give fast reliable near-real-time information and have the ability to handle read and write requests at the same time. Cassandra can meet those needs of storing data and providing fast results for search queries.

Stu Hood, technical lead for the search team in the Email & Apps division of Rackspace, said,

"Cassandra has an approach that hybridizes the Bigtable and Dynamo models, where a lot of its competitors chose to take one path or the other. Over the Bigtable clones, Cassandra has huge high-availability advantages, and no single point of failure. When compared with the Dynamo adherents, Cassandra has the advantage of a more advanced data model, allowing for a single 'row' to contain billions of column/value pairs—enough to fill a machine. You also get efficient range queries for the top level key, even within your values."

And John Quinn, Digg's vice president of engineering, said

"Our primary motivation for moving away from MySQL is the increasing difficulty of building a high-performance, write-intensive application on a data set that is growing quickly, with no end in sight. This growth has forced us into horizontal and vertical partitioning strategies that have eliminated most of the value of a relational database, while still incurring all the overhead."
View Article

Tools:
Add databasejournal.com to your favorites
Add databasejournal.com to your browser search box
IE 7 | Firefox 2.0 | Firefox 1.5.x
Receive news via our XML/RSS feed

Daily News Archives

Comment and Contribute

 


(Maximum characters: 1200). You have characters left.