Titan offers an embedded mode, where Titan starts up Rexster and Cassandra within the same JVM. Could RexConnect also do this, as a very "top" TCP communications layer?
I'm not sure exactly how this would work. RexConnect Server currently runs in its own JVM, and creates a RexsterClient to communicate with Titan/Rexster via the RexPro interface. Could RexConnect create a RexsterTitanServer instead?
If I understand correctly, that this would put RexConnect, Titan, Rexster, and Cassandra all in the same JVM. RexConnect's responsibility would be to pass queries/sessions (sent via TCP) directly to RexsterTitanServer, and return the results. This would cut out the RexsterClient/RexPro layer, and provide performance benefits (I assume) by running in the same JVM.
This will need further investigation. It could be a very powerful feature.
Titan offers an embedded mode, where Titan starts up Rexster and Cassandra within the same JVM. Could RexConnect also do this, as a very "top" TCP communications layer?
I'm not sure exactly how this would work. RexConnect Server currently runs in its own JVM, and creates a
RexsterClient
to communicate with Titan/Rexster via the RexPro interface. Could RexConnect create aRexsterTitanServer
instead?If I understand correctly, that this would put RexConnect, Titan, Rexster, and Cassandra all in the same JVM. RexConnect's responsibility would be to pass queries/sessions (sent via TCP) directly to
RexsterTitanServer
, and return the results. This would cut out theRexsterClient
/RexPro layer, and provide performance benefits (I assume) by running in the same JVM.This will need further investigation. It could be a very powerful feature.