TejonDB, at it's core, is a graph database, and that's very different than a traditional relational database. So what is a graph database and why did we choose such a radical design?
There's a design principle that I wrote about in the SQL Server MVP Deep Dives Vol 2 book. (You can download the section on Generalization here.)
Generalization Yields Flexibility
A graph database makes connections (edges) between objects (nodes). For the purposes of the connections, any object is just another object. Adding a new connection doesn't require a new foreign key, which means that it's much easier to add a new type of connection within a graph database is it is to add a new foreign key within a relational database. Most graph databases apply labels to nodes and connections to identify it's type.
TejonDB takes it a step further by adding object-oriented structure and usage rules to which classes (types) and statuses (statuses), because just adding a label to a node or connection is too slippery for enterprise use.