In this blog post, I'll discuss how NoSQL data modeling is different from traditional relational schema data modeling, and I'll also provide you with some guidelines for document database data modeling.
Document databases, such as MapR-DB, are sometimes called "schema-less" — but this is a misnomer. Document databases don't require the same predefined structure as a relational database, but you do have to define the facets of how you plan to organize your data. Typically, with a NoSQL data store, you want to aggregate your data so that the data can quickly be read together, instead of using joins. A properly designed data model can make all the difference in how your application performs. We have an anecdote at MapR where one of our solution architects worked with a customer, and in a one-hour conversation about schema design, was able to improve access performance by a factor of 1,000x. These concepts matter.
No comments:
Post a Comment