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

The Role of Data Modeling with Key-Value Stores

While the scenario described by Ben O’Steele’s ☞ article — using Redis for log based analytics — might not be interesting to everyone , it made me think once again about the importance of data modeling in the NoSQL space

.

With all the fun and excitement around NoSQL, it’s easy (maybe too easy?) to stuff your data in your preferred NoSQL solution due to its simplicity and speed. But, you should step back and think about:

  • how to model your data
  • what data access patterns will your application need
  • how you deal with data integrity/consistency (what happens if two applications will need to access the same data in read/write mode?)
  • what is the final complexity, performance, scalability of the solution based on the decisions you’ve made to the above points.

It is only then that you should start saving your data!