Software director, architect, and hands-on engineer with decades of experience building systems in the aerospace, energy, and telecoms sectors.
I built MooDb from a belief that, in data-centric systems, the database should be understood, respected, and kept under deliberate control.
In real-world systems, especially at scale, you often depend on carefully designed SQL, stored procedures, constraints, and query-tuning techniques such as temp tables and CTEs. These are not edge cases; they are part of building systems that perform well, scale properly, and behave correctly.
Over time, I found that many larger ORMs move developers away from that reality. They reduce boilerplate, but they also introduce abstraction, hidden behaviour, and distance from the database itself. As systems grow, that distance often turns into friction.
I believe the object-oriented world and the relational world should meet in a more thoughtful way. A database should not simply be shaped around application code. It should be designed well in its own right, retain a meaningful degree of independence, and enforce business rules where they belong — through constraints and database structures.
MooDb is built for that middle ground. It removes repetitive plumbing while keeping database work visible, explicit, and predictable. It is intentionally small, SQL Server-focused, and designed to make working with stored procedures and SQL straightforward rather than hidden.
MooDb is for developers who do not want an ORM to hide the database — they want control, clarity, and a close connection to their data.
