Skip to content
datablend edited this page Apr 20, 2012 · 118 revisions

Blueprints is a collection of interfaces, implementations, ouplementations, and test suites for the property graph data model. Blueprints is analogous to the JDBC, but for graph databases. As such, it provides a common set of interfaces to allow developers to plug-and-play their graph database backend. Moreover, software written atop Blueprints works over all Blueprints-enabled graph databases. Within the TinkerPop software stack, Blueprints serves as the foundational technology for:

  • Pipes: A lazy, data flow framework
  • Gremlin: A graph traversal language
  • Frames: An object-to-graph mapper
  • Furnace: A graph algorithms package
  • Rexster: A graph server

The documentation herein will provide information regarding the use of Blueprints.1 Please join the Gremlin users group at http://groups.google.com/group/gremlin-users for all TinkerPop related discussions.

Blueprints JavaDoc: 1.2
Older JavaDocs: 1.11.00.90.80.70.60.50.40.30.20.1


<!-- neo4j used in this example -->
<dependency>
   <groupId>com.tinkerpop.blueprints</groupId>
   <artifactId>blueprints-neo4j-graph</artifactId>
   <version>1.2</version>
</dependency>

Non-Maven users can get the raw jars from Apache’s Central Repository.

Graph graph = new Neo4jGraph("/tmp/my_graph");
Vertex a = graph.addVertex(null);
Vertex b = graph.addVertex(null);
a.setProperty("name","marko");
b.setProperty("name","peter");
Edge e = graph.addEdge(null, a, b, "knows");
e.setProperty("since", 2006);
graph.shutdown();



1 Blueprints documentation is up to date with the current Blueprints codebase, not with the latest Blueprints release.