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, 14 December 2010
‹ Back

Why NoSQL is hard at The Knot

About:
,
,
,
,

Jason Sirota summarizes concerns expressed by developers, DBAs, and OPs teams related to NoSQL databases:

  1. Developers: NoSQL databases do not separate tiers or concerns
  2. Developers: Sometimes, you can fix app problems just by changing a stored procedure
  3. DBA: There is not as much instrumentation around NoSQL
  4. Reporting: We have to write an app every time we want to show data? 5. Ops: WTF is NoSQL, SQL Server seems pretty fast to me.

Points 1, 2, and 4 are all related to the NoSQL reduced/different data access layer. And as much as we like to tout separation of OLTP and OLAP systems, we need to agree that there are a lot of companies out there that do not do it (lots of reasons) thus validating these concerns.

Original title and link: Why NoSQL is hard at The Knot (NoSQL databases © myNoSQL)

via: http://jasonsirota.posterous.com/why-nosql-is-hard-at-the-knot