Java Embedded In memory graphdb's
up vote
0
down vote
favorite
We are looking for option to represent our relation tables in graphdb (for certain use cases graph query will be less complex than sql). We want capability were on tomcat startup we can quickly build graph using some files (like csv) and then keep it in main memory for querying. We should also be able to refresh in memory representation on fly in case some data change happen. We have evaluated couple option as below
neo4j embedded - it's perfect but consuming lot of main memory.
300-400 MB of data almost take 2-3 gb of main memory.netflix-graph(https://github.com/Netflix/netflix-graph) - Good for our use case but project seems to be out of maintenance. Since it has not been widely used we are not sure what all issues it have and if we can use it for prod.
Apart from above two option can folks here suggest alternatives which we can evaluate.
TIA
netflix neo4j-embedded
add a comment |
up vote
0
down vote
favorite
We are looking for option to represent our relation tables in graphdb (for certain use cases graph query will be less complex than sql). We want capability were on tomcat startup we can quickly build graph using some files (like csv) and then keep it in main memory for querying. We should also be able to refresh in memory representation on fly in case some data change happen. We have evaluated couple option as below
neo4j embedded - it's perfect but consuming lot of main memory.
300-400 MB of data almost take 2-3 gb of main memory.netflix-graph(https://github.com/Netflix/netflix-graph) - Good for our use case but project seems to be out of maintenance. Since it has not been widely used we are not sure what all issues it have and if we can use it for prod.
Apart from above two option can folks here suggest alternatives which we can evaluate.
TIA
netflix neo4j-embedded
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We are looking for option to represent our relation tables in graphdb (for certain use cases graph query will be less complex than sql). We want capability were on tomcat startup we can quickly build graph using some files (like csv) and then keep it in main memory for querying. We should also be able to refresh in memory representation on fly in case some data change happen. We have evaluated couple option as below
neo4j embedded - it's perfect but consuming lot of main memory.
300-400 MB of data almost take 2-3 gb of main memory.netflix-graph(https://github.com/Netflix/netflix-graph) - Good for our use case but project seems to be out of maintenance. Since it has not been widely used we are not sure what all issues it have and if we can use it for prod.
Apart from above two option can folks here suggest alternatives which we can evaluate.
TIA
netflix neo4j-embedded
We are looking for option to represent our relation tables in graphdb (for certain use cases graph query will be less complex than sql). We want capability were on tomcat startup we can quickly build graph using some files (like csv) and then keep it in main memory for querying. We should also be able to refresh in memory representation on fly in case some data change happen. We have evaluated couple option as below
neo4j embedded - it's perfect but consuming lot of main memory.
300-400 MB of data almost take 2-3 gb of main memory.netflix-graph(https://github.com/Netflix/netflix-graph) - Good for our use case but project seems to be out of maintenance. Since it has not been widely used we are not sure what all issues it have and if we can use it for prod.
Apart from above two option can folks here suggest alternatives which we can evaluate.
TIA
netflix neo4j-embedded
netflix neo4j-embedded
asked Nov 11 at 7:32
Rishi Saraf
716616
716616
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f53246713%2fjava-embedded-in-memory-graphdbs%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