Simple production database alternatives for small Gremlin.Net applications
Hi!
What production database alternatives are there out there for small DotNet applications with Gremlin.Net?
The reason why I'm asking is because there does not seem to be any easy to use and maintain solutions: they either require a lot production infrastructure and maintenance (JanusGraph), have high enterance fees (Datastax Enterprice), are only partially supporting old versions og Gremlin (CosmosDB) or are lacking pre-defined serialisers for DotNet (e.g ArangoDB).
I might be misjudging hugely in the above paragraph, but I hope I it gives an explanation of the issue with our current use case: As a small project team building a small Gremlin application in C# that needs a way of running our application in a production environment for small-scale usage and demos: how can we do that most efficiently?
PS: We would have tried out AWS Neptune DB if we were not bound to using Azure by business policy.
Any tips and advice appreciated!
3 Replies
you said a "small DotNet Application" but does that also mean a small database? perhaps you could say more about what you need from the data storage side in the way of features?
Hi @spmallette ! 😊 That is some good information to add.
We have very few hard requirements as of now. We need to be able to do live-queries (with "UI-compatible response times") on a small, sparsely connected graph. (We are modelling Electrical Utility Grids for an startup/innovation project.)
At the moment we are using Janusgraph for development, with no special features apart from vertices and edges with properties and labels. Ideally the DB would support VertexIds of UUID type, but we are currently solving that by a custom property with index and uniqueness constraint in JanusGraph.
With respect to graph size, it is often discussed in terms of number of edges in the graph - how big is your "small" graph and is the graph static?