ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close
Thursday, 18 February 2010
‹ Back

Understanding the NoSQL movement

About:
,
,
,

While over MyNoSQL we love all things NoSQL, I still think that scaling RDBMSes is an interesting topic some of the techniques used being the same in the NoSQL space. PCPro has published ☞ an article signed by Ian Wrigley that talks about the various steps for scaling a relational database (each step is accompanied by a short description and a nice diagram):

  • master - slave
  • master - master, plus master - slave
  • horizontal partitioning (sharding)
  • vertical partitioning
  • transition to NoSQL (nb: this is actually my note. Anyway, please do keep in mind that scalability should not be the only reason for taking a look at NoSQL solutions)

In my opinion, the part about NoSQL itself is not as good or consistent as the first part on scaling RDBMSes and so I have found the title a bit misleading.

via: http://www.pcpro.co.uk/realworld/355477/understanding-the-nosql-movement/