{"id":9774,"date":"2020-01-15T07:00:39","date_gmt":"2020-01-15T15:00:39","guid":{"rendered":"http:\/\/formtek.com\/blog\/?p=9774"},"modified":"2019-11-19T09:07:18","modified_gmt":"2019-11-19T17:07:18","slug":"multi-model-databases-the-swiss-army-knife-of-data-architecture","status":"publish","type":"post","link":"https:\/\/formtek.com\/blog\/multi-model-databases-the-swiss-army-knife-of-data-architecture\/","title":{"rendered":"Multi-Model Databases: The Swiss Army Knife of Data Architecture"},"content":{"rendered":"\n

Multi-model databases<\/a> 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.<\/p>\n\n\n\n

Ken Krupa<\/a>, CTO at MarkLogic, said that<\/a> “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.”<\/p>\n\n\n\n

Sanjeev Mohan<\/a>, analyst at Garner, said that<\/a> “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\u2019s not easy to link graph databases with relational databases. But the movement towards multi-model is only going to increase.” \n\n<\/p>\n\n\n\n

Marklogic quotes one analyst,<\/a> saying that “it\u2019s no longer about relational vs. non, we\u2019re in the multi-model database generation now.”<\/p>\n\n\n\n

<\/p>\n

\"Digg<\/a><\/div>
\"Reddit<\/a><\/div>
\"Stumble<\/a><\/div>
\"Buzz<\/a><\/div>
\"Vote<\/a><\/div>
\"Share<\/a><\/div>
\"Bookmark<\/a><\/div>
\"Kick<\/a><\/div>
\"Shout<\/a><\/div>
\"Share<\/a><\/div>
\"Bookmark<\/a><\/div>
\"Post<\/a><\/div>
\"Google<\/a><\/div><\/div>","protected":false},"excerpt":{"rendered":"

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…<\/span><\/p>\n

Read more ›<\/a><\/div>\n

<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35],"tags":[],"class_list":["post-9774","post","type-post","status-publish","format-standard","hentry","category-structured-data"],"_links":{"self":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/9774","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/comments?post=9774"}],"version-history":[{"count":1,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/9774\/revisions"}],"predecessor-version":[{"id":9775,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/9774\/revisions\/9775"}],"wp:attachment":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/media?parent=9774"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/categories?post=9774"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/tags?post=9774"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}