There is no consensus as to what the ideal graph structure is for storing data. It depends on the nature of the data and the purposes for which it's used. Triplestore, Property Graph, HyperGraph... they all have their strengths and their problems.
Your ideal structure may contain features of all of these graph types, and more besides. With GraphBase Enterprise Edition you can configure light-weight primitives to give you the structure you need. Even our simplified Agility Edition gives greater data-modelling power than any other DBMS and any other Graph Database solution.
Enterprise Edition also lets you configure how your graph is indexed - including support for subsumption. Take a look at the Community Semantic Framework to get a sense for how this works.
GraphBase lets you store objects directly within vertices. Enterprise configurations allow these objects to become first-class citizens within GraphBase, and "Agent" mechanisms allow their logic to be distributed amongst GraphBase server Nodes.
You can also embed simple high-performance data structures within graph vertices to handle high volume real-time and "big data" problems. This is a strategy used to dramatic effect by our i6 Real-Time Intelligence product.
Versatile Transaction Control and Security
Agility Edition enforces full transaction (ACID) semantics. These, however, can create significant performance issues - particularly across a distributed data store. That's why most new NoSQL database products don't support them.
The GraphBase Enterprise Security Framework allows you to specify which parts of your GraphBase graph need locks, rollback and other transactional support - and which parts don't. Get ACID where it matters, Eventual Consistency where it doesn't - and the best possible performance at all times.
The Security Framework also gives you fine-grained control over who can see and modify which parts of your GraphBase graph.