Impedance Mismatch
Summary: The disconnect between the object-oriented models used in application code and the table/row/column model used by relational databases.
Sources: raw/chapter2
Last updated: 2026-04-15
If data is stored in relational tables, an awkward translation layer is required between the objects in the application code and the database model. This is often called an impedance mismatch, a term borrowed from electronics (source: chapter2, p. 29-30).
Mitigation Strategies
- Object-Relational Mapping (ORM): Frameworks like ActiveRecord and Hibernate reduce boilerplate code for this translation but cannot completely hide the differences between the two models (source: chapter2, p. 30).
- document-model: By storing data in a format closer to application-level objects (like JSON), the document model can reduce the impedance mismatch (source: chapter2, p. 31).