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
Tuesday, 10 May 2011
‹ Back

A BigData Problem

About:
,

Bradford Stephens[1]:

You know you have a BigData problem:

  • when your hardware budget is growing exponentially
  • when you have so much data in the database that you keep hiring consultants and operations guys to mitigate the effects of periodic slowdowns.
  • when developers want to produce new features but they’re spending more time maintaining the systems than working on them … the engineers can’t seem to deliver the system’s potential.

  1. CEO of Drawn to Scale, LusciousPear  ↩

Original title and link: A BigData Problem (NoSQL databases © myNoSQL)

via: http://www.informationweek.com/news/software/info_management/229403098?cid=RSSfeed_IWK_ALL