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
Wednesday, 29 September 2010
‹ Back

What Can We Learn from JPMorgan Database Outage?

About:
,

If you read the reports on JPMorgan database outage[1] and leave aside the products, I think there is an interesting scenario that you should test your NoSQL database. So here it is: if a node gets corrupted, will this issue get replicated/mirrored to other nodes? Or differently put: what mechanisms are available for checking the status and correctness of a node?

  1. For example Curt Monash’s ☞ report  (↩)

Original title and link: What Can We Learn from JPMorgan Database Outage? (NoSQL databases © myNoSQL)