Clone this wiki locally
Pixy is a declarative graph query language that works on any Blueprints-compatible graph database. The Blueprints API provides a common interface to over a dozen graph databases, including Neo4J, Titan, InfiniteGraph, OrientDB, DEX and Bitsy. By leveraging the Tinkerpop software stack (Blueprints, Gremlin, Pipes), Pixy offers a portable, high-performance alternative to proprietary query languages like Cypher (Neo4J).
Pixy enables complex pattern matching and logic programming on graph databases by translating PROLOG-style rules and goals to Gremlin pipelines that represent graph traversal operations. Queries in Pixy can also be seemlessly integrated into Gremlin expressions. The combination of Pixy and Gremlin gives the programmer the full power of two graph querying paradigms, viz. graph pattern matching and graph traversal.
Pixy is an open-source contribution from LambdaZen, the maker of the Bitsy Graph Database, and is available under the Apache 2.0 license. The project was motivated from the need for a portable graph query language based on pattern matching (rather than graph traversal) that could attract a wider audience to the Tinkerpop software stack. Although all testing is done with Bitsy, the goal of this project is to be portable and vendor-neutral.
Please report your feedback, comments and suggestions to pixy (at) lambdazen.com, or as issues in this project. You can report bugs using Pixy on any Blueprints-compatible graph database. Contributions (pull requests) from vendors and enthusiasts are welcome.
- Advantages over pure Gremlin
- Advantages over Cypher (the Neo4J query language)
- 3 Myths about graph query languages Busted by Pixy: A presentation on Slideshare
- Getting Pixy
- Learning Pixy
- Integrating Pixy
- Blog on Pixy and first-order logic
What's with the name
Pixy. A fairylike or elfin creature, especially one that is mischievous; a playful sprite.
Synonym for Gremlin
Acronym for "Patterns in X Y"