Congrats on funding round, we need more options in this space. I'm a Neo user today, and I've said before that while I don't think most people will switch to graph databases, at some point I do think most new projects will use them. I chose Neo precisely because of py2neo.
The decision to adapt GraphQL instead of supporting Cypher, what would you say were the big trade offs?
As a startup, your price point is in the 20k/y ballpark, but GrapheneDB/Neo comes in a lot lower. What would I get for paying that much more?
I find that the audience for something that operates at the level of abstraction that a graph does tends to be different than the user who makes decisions based on lower-level features. e.g. design level problems vs. optimization problems.
Would you say more that you can get Mongo and Redis (+redisgraph) users to switch to Dgraph, or instead more that the main customers for graph databases are still in school right now and deciding what tech skills will underpin their careers?
Fascinating space and looking forward to trying the product.
The decision to adapt GraphQL instead of supporting Cypher, what would you say were the big trade offs?
As a startup, your price point is in the 20k/y ballpark, but GrapheneDB/Neo comes in a lot lower. What would I get for paying that much more?
I find that the audience for something that operates at the level of abstraction that a graph does tends to be different than the user who makes decisions based on lower-level features. e.g. design level problems vs. optimization problems.
Would you say more that you can get Mongo and Redis (+redisgraph) users to switch to Dgraph, or instead more that the main customers for graph databases are still in school right now and deciding what tech skills will underpin their careers?
Fascinating space and looking forward to trying the product.