Access and Feeds

Multi-Model Databases: The Swiss Army Knife of Data Architecture

By Dick Weisinger

Multi-model databases are able to store, index and query across more than one model. Multi-model means that the database uses different database architectures to model data in more than one way, like standard relational, hierarchical, document-oriented, graph or key-value. The rationale is that each of the different types of models excel at different use cases.

Ken Krupa, CTO at MarkLogic, said that “all of those models are important, and you want to maintain them all. You want to harmonize them in a way as opposed to trying to mash them into a single model.”

Sanjeev Mohan, analyst at Garner, said that “there will be some types of databases that are not ideally suited for multi-model and they may stay separate, such as graph databases, which are usually a different structure and it’s not easy to link graph databases with relational databases. But the movement towards multi-model is only going to increase.”

Marklogic quotes one analyst, saying that “it’s no longer about relational vs. non, we’re in the multi-model database generation now.”

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Leave a Reply

Your email address will not be published. Required fields are marked *

*