I worked on a project which employed the Gremlin API on an Azure Cosmos DB instance. This configuration worked (largely) seamlessly, though it is worth accentua

I worked on a project which employed the Gremlin API on an Azure Cosmos DB instance. This configuration worked (largely) seamlessly, though it is worth accentuating how we worked explicitly with graphs and consequently benefited from being able to actually store and query our data as graphs. An alternative could have been Neo4j, which, based on preliminary research, would have done the job, too. Overall, it was a nice, new experience which arguably presented a learning curve. One piece of advice, however, would be to thoroughly evaluate your requirements and strongly consider whether you actually need a graph database in the first place! If you are dealing with an excessive amount of interconnected relationships, definitely consider this option. If not, chances are you will have something functioning faster with a conventional database.