Sounds like ☞ Gremlin with Ruby’s syntactic sugar:
Let’s get two very fundamental differences out of the way first. First, Pacer uses Ruby as it’s language, employing method chaining to define traversal routes while Gremlin defines its own using a combination of xpath-like traversal definitions with its own procedural syntax for other functions. Secondly, Pacer does not have the concept of a current vertex or a current graph; the starting point of any traversal is explicit and there are no special variables like Gremlin’s $g and $.
Original title and link: Pacer: Gremlin with Ruby Flavor (NoSQL databases © myNoSQL)