GrapheneDB vs Graph Story on Heroku
I have no experience with Graph DB applications, but I am trying to write one. I intend to post on Heroku
.
I see that there are 2 DB DB service providers with free plans, but I cannot decide which one to use, they both sell themselves using different attributes and I cannot compare! For example:
-
GrapheneDB only mentions the node limit and the number of links limit and the request time limit. But nothing about the storage limit.
-
Graph Story mentions RAM limit, `storage limitation and data transfer limitation.
Other properties are mentioned as well, but they are not comparable between both vendors.
Has anyone tried any of these services on Heroku
and could share their experiences?
EDIT : I found this page which gives an idea of how much space is required for neo4j.
source to share
I will tackle the answer to this question, being as objective as possible, since I and some of the other frequent responders here have a good relationship with both providers.
Both have their pros and con, and I think looking only at the Heroku side might not be a good choice.
There is also one difference between what you need to know, GraphStory provides Neo4j Enterprise and GrapheneDB provides Neo4j Community, that's a fact. However, I personally think that if you run neo4j on heroku then you do not need to take, because Neo4j "enterprise" users are using their own clustering environment on servers with "real" RAM and SSD, which can actually be managed like providers with license and support.
You are talking about the storage limit. The good thing is that storage depends on your number of nodes, relationships and properties in the database, so if there is a 1000 node limit, you don't have to worry about the storage limit I'm thinking about.
I've tried both on heroku, and aside from node restrictions, there is not much performance difference in deploying free speakers.
If you are a startup the launch of Neo4j on heroku is great, if you take the paid plan, of course both providers have great support and both reward their long-term customers.
If you only look at free dinosaurs, then you don't have to worry about the constraints, because it will just be LIMITED, by any means!
Outside of Heroku, here are a few things I looked at:
- GrapheneDB works on all platforms including Azure which is great stuff.
- GraphStory launches enterprise so you can use high performance cache
- GrapheneDB has an API available to create neo4j servers on the fly and destroy.
- Depending on your location, you may need support from Europe or the United States.
- basic plans, on both, suffer some lag or load time when not in use for a long time.
- Both have spatial support
- Both are actors of the Neo4j community with cool stuff, you can meet them in reality :)
Now you can test them both for free !!!
source to share
I tried one CRUD app yesterday, deployed in 2 Heroku apps, one with Graph Story and another with GrapheneDB.
- I tracked with NewRelic and I found that the Graph Story app has a 1 to 2 second wait environment variable, instead the GrapheneDB service only needs 20 to 40ms to perform the same operations.
-
I wanted to try to pay the plan in a few minutes on Graph Story, but for that you need to contact help and wait for an unknown time. Instead, GrapheneDB allows you to change the plan yourself without any problem.
-
I tried to export the db to Graph Story, but the operation is not real-time: you have to wait for the link to be emailed. I run the operation 2 times, but the email hasn't arrived yet after 10 o'clock. Instead, GrapheneDB exports immediately, without waiting for alarming emails.
source to share
Graph Story offers the following features that set it apart from other offerings:
- Graph Story Offers Enterprise Edition Neo4j
- No restrictions on nodes or relationships on a free plane
- The maximum request time is 30 seconds.
Sure, you wouldn't want to use the free plan in production, but it's great for proof-of-concept, learning Neo4j, small hobby projects, etc.
(Full disclosure: I'm the CTO at Graph Story.)
source to share