anchor.diff:  <<connecting-embedded,embedded>> usage, lambdas can be leveraged directly:
   
   [source,java]
  +----
   g.V().out("knows").map(t -> t.get().value("name") + " is the friend name") <1>
   g.V().out("knows").sideEffect(System.out::println) <2>
   g.V().as("a").out("knows").as("b").select("b").by((Function<Vertex, Integer>) v -> v.<String>value("name").length()) <3>
  +----
   
   <1> A Java `Function` is used to map a `Traverser<S>` to an object `E`.
   <2> Gremlin steps that take consumer arguments can be passed Java method references.
  
positive.code: language's JSR-223 `ScriptEngine` implementation.
  
  [source,java]
  g.V().out("knows").map(Lambda.function("it.get().value('name') + ' is the friend name'"))
  g.V().out("knows").sideEffect(Lambda.consumer("println it"))
  g.V().as("a").out("knows").as("b").select("b").by(Lambda.<Vertex,Integer>function("it.value('name').length()"))
  
  Finally, Gremlin `Bytecode` that includes lambdas requires that the traversal be processed by the
  `ScriptEngine`. To avoid continued recompilation costs, it supports the encoding of bindings, which allow Gremlin
  
negative.code: server configuration can be managed by the `alias` method on `Client` as follows:
  
  [source,java]
  ----
  Client g1Client = client.alias("g1")
  Client g2Client = client.alias("g2")
  g1Client.submit("g.V()")
  g2Client.submit("g.V()")
  ----
  
  The above code demonstrates how the `alias` method can be used such that the script need only contain a reference
  to "g" and "g1" and "g2" are automatically rebound into "g" on the server-side.
  