The System as a Program: fusing the database and the programming language
A proposal to fuse the database and programming language into a single system where the entire system state is treated as a program, eliminating the impedance mismatch between application code and data storage.
Background
- This article is about the "Database as a Program" paradigm, an approach that merges the database and the programming language into a single, persistent system. Instead of a traditional database that stores data and an application that processes it separately, the data and the logic live together as one long-running program.
- The key idea is that the database is not a passive storage layer but an active, stateful program that can be queried and modified directly. This eliminates the "impedance mismatch" between object-oriented code and relational tables.
- The author, Thomas Cambra, is likely a developer or researcher exploring alternative architectures. The post reflects ongoing discussions in the software engineering community about simplifying stack complexity.
- Prior context: Most modern web apps use a separate database (like PostgreSQL) alongside a backend framework (like Rails or Django). This separation creates translation layers (ORM) that can be slow and brittle. "The System as a Program" is a niche but influential idea that aims to collapse those layers into one coherent runtime.