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, 22 December 2011
‹ Back

NoSQL Databases: 6 Business and Technical Reasons for a New Set of Requirements

About:
,
,

Here are some technical reasons why traditional relational database vendors are getting challenged:

  1. Scale: The biggest driver of the new generation of data management systems was unprecedented scale.
  2. Disk Capacities have exploded and Random Disk Accesses have gotten cheaper
  3. Fixed Schema is too rigid
  4. First Normal Form is too restrictive/rich
  5. Columnar Stores: It may sometimes be desirable to store together related columns which are accessed together.
  6. Programmatic Access is also important

Great post with a somehow bogus conclusion though.

Original title and link: NoSQL Databases: 6 Business and Technical Reasons for a New Set of Requirements (NoSQL database©myNoSQL)

via: http://www.binfikr.com/?p=102