Tinkerpop embedded implementation for production
up vote
1
down vote
favorite
I've got a use case where I wouldn't need a full-blown features of a graph db. I would already receive a network (connected nodes and edges) from a datasource and all I'd have to do is to apply a few graph operations on it (eg: Shortest Path between 2 nodes, Discover relationships etc). The network size isn't huge (max 200 nodes). I was wondering if I can use an embedded Tinkerpop for this? Anything I should watch out for? This is a production application and will be used in a highly multithreaded context etc etc.
graph-databases tinkerpop tinkerpop3
add a comment |
up vote
1
down vote
favorite
I've got a use case where I wouldn't need a full-blown features of a graph db. I would already receive a network (connected nodes and edges) from a datasource and all I'd have to do is to apply a few graph operations on it (eg: Shortest Path between 2 nodes, Discover relationships etc). The network size isn't huge (max 200 nodes). I was wondering if I can use an embedded Tinkerpop for this? Anything I should watch out for? This is a production application and will be used in a highly multithreaded context etc etc.
graph-databases tinkerpop tinkerpop3
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I've got a use case where I wouldn't need a full-blown features of a graph db. I would already receive a network (connected nodes and edges) from a datasource and all I'd have to do is to apply a few graph operations on it (eg: Shortest Path between 2 nodes, Discover relationships etc). The network size isn't huge (max 200 nodes). I was wondering if I can use an embedded Tinkerpop for this? Anything I should watch out for? This is a production application and will be used in a highly multithreaded context etc etc.
graph-databases tinkerpop tinkerpop3
I've got a use case where I wouldn't need a full-blown features of a graph db. I would already receive a network (connected nodes and edges) from a datasource and all I'd have to do is to apply a few graph operations on it (eg: Shortest Path between 2 nodes, Discover relationships etc). The network size isn't huge (max 200 nodes). I was wondering if I can use an embedded Tinkerpop for this? Anything I should watch out for? This is a production application and will be used in a highly multithreaded context etc etc.
graph-databases tinkerpop tinkerpop3
graph-databases tinkerpop tinkerpop3
edited Nov 10 at 12:42
Stanislav Kralin
7,39541639
7,39541639
asked Nov 9 at 21:35
user1189332
616820
616820
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
When you say "emebedded TinkerPop" I assume that you mean the in-memory graph database that it provides called "TinkerGraph". If that is correct, then I would say that it can be used for the kind of use case that you describe. If you have a small graph that fits in-memory and you don't need any bells and whistles, it should be a good fit and likely the best choice of any TinkerPop-enabled graph.
The only thing you should be aware of is that TinkerGraph is not thread-safe for mutations. You don't want to have multiple threads mutating the graph at the same time. For the graph size you describe, it sounds as though it should be cheap to clone copies of the graph to share among threads if you need to.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
When you say "emebedded TinkerPop" I assume that you mean the in-memory graph database that it provides called "TinkerGraph". If that is correct, then I would say that it can be used for the kind of use case that you describe. If you have a small graph that fits in-memory and you don't need any bells and whistles, it should be a good fit and likely the best choice of any TinkerPop-enabled graph.
The only thing you should be aware of is that TinkerGraph is not thread-safe for mutations. You don't want to have multiple threads mutating the graph at the same time. For the graph size you describe, it sounds as though it should be cheap to clone copies of the graph to share among threads if you need to.
add a comment |
up vote
2
down vote
When you say "emebedded TinkerPop" I assume that you mean the in-memory graph database that it provides called "TinkerGraph". If that is correct, then I would say that it can be used for the kind of use case that you describe. If you have a small graph that fits in-memory and you don't need any bells and whistles, it should be a good fit and likely the best choice of any TinkerPop-enabled graph.
The only thing you should be aware of is that TinkerGraph is not thread-safe for mutations. You don't want to have multiple threads mutating the graph at the same time. For the graph size you describe, it sounds as though it should be cheap to clone copies of the graph to share among threads if you need to.
add a comment |
up vote
2
down vote
up vote
2
down vote
When you say "emebedded TinkerPop" I assume that you mean the in-memory graph database that it provides called "TinkerGraph". If that is correct, then I would say that it can be used for the kind of use case that you describe. If you have a small graph that fits in-memory and you don't need any bells and whistles, it should be a good fit and likely the best choice of any TinkerPop-enabled graph.
The only thing you should be aware of is that TinkerGraph is not thread-safe for mutations. You don't want to have multiple threads mutating the graph at the same time. For the graph size you describe, it sounds as though it should be cheap to clone copies of the graph to share among threads if you need to.
When you say "emebedded TinkerPop" I assume that you mean the in-memory graph database that it provides called "TinkerGraph". If that is correct, then I would say that it can be used for the kind of use case that you describe. If you have a small graph that fits in-memory and you don't need any bells and whistles, it should be a good fit and likely the best choice of any TinkerPop-enabled graph.
The only thing you should be aware of is that TinkerGraph is not thread-safe for mutations. You don't want to have multiple threads mutating the graph at the same time. For the graph size you describe, it sounds as though it should be cheap to clone copies of the graph to share among threads if you need to.
answered Nov 12 at 11:45
stephen mallette
24.3k32776
24.3k32776
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53233546%2ftinkerpop-embedded-implementation-for-production%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown