Grakn developer here. That's interesting, do you have any particular graph database in mind? Grakn runs fine on a single machine. One of the core architectural

Grakn developer here. That's interesting, do you have any particular graph database in mind? Grakn runs fine on a single machine. One of the core architectural points is that the engine should not be too tightly bound to the storage layer. Currently we rely on Cassandra for storage but we are experimenting with other solutions. The answer to your last question depends on what query you are performing. If the domain you are modelling is represented naturally as a graph, then you can expect much better performance than PostgreSQL (we'll publish some benchmark results soon).