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

Document Databases and the Impedance Mismatch with the Object World

One of the most often mentioned issues reported by software engineers working with relational databases from object-oriented languages is the object-relational impedance mismatch. Document databases adopters are saying that one benefit of document stores is that there is no impedance mismatch between the object and document worlds.

I don’t think this is entirely true.

Firstly, the numerous object-document mapping frameworks are a proof people are still using tools to convert between objects and documents. CouchDB and MongoDB already have many mapping frameworks available in the most popular languages.

Secondly, if you consider the highly connected hierarchical object model you’ll realize that mapping it into the document model is not consistent. It requires applying specific domain knowledge and involves different strategies depending on usage scenarios.

So, what is my point? Document databases are not solving the impedance mismatch with the object world. All they do is offering more flexibility in converting from one to another.

Original title and link: Document Databases and the Impedance Mismatch with the Object World (NoSQL databases © myNoSQL)