Threaded Operations - Quarkus
Joe Obernberger
Hi All - building a REST
service using Quarkus to handle requests that operate on a graph.
The current approach is:
Static class that contains the JanusGraph and GraphTraversalSource objects that are created once per VM. Use those objects when a request comes into add vertices, edges, properties, and when completed, commit.
Since quarkus can be called via multiple threads, what is the best approach to make sure the transactions are thread safe? I'm looking here (https://docs.janusgraph.org/interactions/transactions/), but not sure of the best approach.
Thank you!
-Joe
Static class that contains the JanusGraph and GraphTraversalSource objects that are created once per VM. Use those objects when a request comes into add vertices, edges, properties, and when completed, commit.
Since quarkus can be called via multiple threads, what is the best approach to make sure the transactions are thread safe? I'm looking here (https://docs.janusgraph.org/interactions/transactions/), but not sure of the best approach.
Thank you!
-Joe
