From the readme file:
Pilot is a graph database operator that allows you to perform common application-level operations on graph databases without delving into the details of their implementation or requiring knowledge of the component technologies.
Pilot aims to support graph databases conforming to the property graph model. Pilot employs technologies from the Tinkerpop stack — specifically Blueprints and Gremlin — for general access and manipulation of the underlying graph database, but also uses native graph database APIs to further optimize performance for certain operations. In addition, Pilot also handles multithreading and transaction management, while keeping all of these abstracted away from the calling application. As such, Pilot is ideally suited for use in concurrent web applications.
- Supported graph database providers:
- OrientDB
- Neo4j
- Tinkergraph (the Blueprints in-memory reference implementation)
- (others may be added in future if there is demand)
- Some of the functionality currently supported by Pilot include:
- Get edges between given vertices
- Get neighbors of a given vertex
- Retrieving vertices corresponding to some properties (see Property Graph Model)
- Transaction management
- Thread synchronization for multithreaded access
- Large commit optimization
- Application profiling
- Planned additions:
- Support for Furnace
- FOAF
- DFS
- BFS
Graph databases aren’t a new idea. I don’t have the reference at hand but once ran across a relational database that was implemented as a hypergraph. It may be that computing power has finally gotten to the point that graph databases, or at least their capabilities, will be the common expectation.