ORM: The Virtual Object Database Layer

Why it exists

Relational databases store data in a structured format. Object-oriented programming languages store data as objects in memory. These two models are incompatible. Without a conversion technique, a program must manually move data between the database and memory. Object-relational mapping exists to automate this conversion, creating a virtual object database that can be used from within the program.

The mental model

Think of ORM as a translation layer between two worlds. On one side is the relational database. On the other is the memory of an object-oriented programming language. The ORM creates a virtual object database that your program interacts with directly. It handles the conversion so your code can work with memory objects instead of the raw data stored relationally.

How it works

The technique converts data between the relational database and program memory. When data moves from the database into the program, the ORM transforms it into objects in the memory of the object-oriented language. When the program modifies those memory objects, the ORM converts the changes back into a form the relational database can store. This bidirectional conversion creates the illusion of a native object database inside the program.

When to use it

Use this technique when you want to access a relational database through the object-oriented paradigm. It is appropriate when you prefer to reason about data as objects in memory rather than as raw relational data. It is also useful when you want the program to treat the database as a virtual object database that can be used from within the program.

When not to use it

Avoid this technique when the abstraction adds more cost than value. If your problem is naturally relational and does not benefit from an object representation, the conversion step is unnecessary overhead. It is also a poor fit when you need explicit control over the conversion between the database and memory, because the virtual object database hides those details from you.

One canonical example

Consider a program that reads data from a relational database. Without the technique, the program must manually convert the database data into objects in memory. With an ORM, the program requests data through the virtual object database, and the technique automatically converts the relational data into objects in the memory of the object-oriented programming language. When the program changes those objects, the ORM converts the memory changes back for the relational database.