A toolkit that enables querying Gremlin graph databases using the Cypher query language.
Cypher for Gremlin is a translation toolkit that enables querying Gremlin graph databases using the Cypher query language. It translates Cypher queries into Gremlin representations, allowing developers to use Neo4j's industry-standard query syntax on any Apache TinkerPop-compatible database like JanusGraph, AWS Neptune, or Azure Cosmos DB. The project solves the problem of vendor lock-in by bridging two major graph query paradigms.
Graph database developers and teams who are familiar with Cypher but need to work with Gremlin-based databases, or those seeking to standardize on Cypher across multiple graph backends.
Developers choose Cypher for Gremlin because it provides a seamless way to use Cypher's intuitive syntax on Gremlin databases, reducing the learning curve and enabling code portability. Its toolkit approach—with server plugins, client wrappers, and Neo4j driver compatibility—offers flexibility for both client-side and server-side translation.
Cypher for Gremlin adds Cypher support to any Gremlin graph database.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables Cypher querying on any TinkerPop-compatible database like AWS Neptune and Azure Cosmos DB, reducing vendor lock-in as described in the toolkit.
Implements Neo4j Java API interfaces, allowing developers to reuse Neo4j driver code with Gremlin backends, easing migration efforts.
Provides both Gremlin Server plugins for server-side processing and client-side translation options, offering deployment versatility across environments.
Achieves 90% TCK coverage with extensions, supporting core Cypher clauses like MATCH and CREATE, ensuring reliable translation for common queries.
The README explicitly states the transpiler is 'not maintained anymore,' meaning no updates, bug fixes, or official support, posing risks for adoption.
Excludes some Cypher features such as temporal types, and TCK coverage is incomplete, limiting advanced query capabilities and compatibility.
Full Cypher support requires Gremlin extensions on databases like JanusGraph, adding setup complexity and potential compatibility hurdles.
Translation from Cypher to Gremlin introduces overhead, which can impact query performance compared to native Gremlin executions, especially in high-load scenarios.