Hello,
> I was wondering where things left off for this work. Mostly because
> distributed Gremlin OLTP sounded promising but also because we use both DSE
> Graph and Akka at my work.
It still is very promising work.
> I noticed in Git that it hasn't been worked on lately. Did you hit a wall
Hi Marko, all,
I was wondering where things left off for this work. Mostly because
distributed Gremlin OLTP sounded promising but also because we use both DSE
Graph and Akka at my work.
I noticed in Git that it hasn't been worked on lately. Did you hit a wall
with this approach? If so, can an
Hi,
> > Thus, I don’t think GremlinServer really needs to come into play.
>
> Unless i'm missing something, I'm not sure we should say it quite that way -
> that's a bit more jvm-centric sounding. So as not to be confused, non-jvm
> GLVs would still require Gremlin Server, right?
I think it ge
Gremlin Server should probably start the akka cluster (of course, i still
don't have a solid understanding of the clustering capabilities of akka
just yet). .I also wonder if there is any value to Gremlin Server embedding
akka so it could piggyback on some of the features akka has (e.g. perhaps
gre
Hi,
> How will this get deployed? Each database instance (alternatively
> gremlin-server) shipping a version of akka-actor and akka-cluster?
This is a good question. As I’m seeing it lately, I think we treat it just like
spark-gremlin/. That is, lets assume a multi-machine graph database:
Hello,
> I have only one idea: do traversal API users still really have to know
> whether they use a GraphComputer or GraphActors? In other words, can the
> withEngine options not just be some illuminating token constants for users
> that just want to have the traversal() returned (LOCAL, LOCAL
