求推荐适用的Azure Cosmos DB Gremlin Fluent SDK

Hey there! Sorry to hear that random fluent SDK didn't work out for you—let me break down the most reliable options tailored for Azure Cosmos DB Graph that the community swears by:

1. Microsoft's Official Gremlin .NET SDK (with Fluent API Support) #

This is the gold standard since it’s built and maintained directly by Microsoft, so you get full compatibility with Cosmos DB’s Graph API features. It seamlessly integrates with both fluent-style queries and raw string Gremlin queries, which is perfect if you’re transitioning from string-based operations.

Here’s a quick example of how you might use its fluent API to query and modify data:

// Initialize the client with your Cosmos DB credentials
var gremlinClient = new GremlinClient(new GremlinServer("<your-cosmos-endpoint>", 443, true, "/dbs/<db-name>/colls/<coll-name>", "<auth-key>"));

// Fluent query: Find a user and their followed connections
var traversal = g.V().HasLabel("user").Has("id", "rasmus").OutE("follows").InV().HasLabel("user");
var resultSet = await gremlinClient.SubmitAsync<dynamic>(traversal);

It handles Cosmos-specific nuances like partition keys and request unit (RU) management out of the box, so you won’t hit unexpected compatibility snags.

2. Gremlin.Net.CosmosDb (Community-Maintained) #

If you want a tool explicitly optimized for Cosmos DB’s quirks, this community-driven library is a great pick. It extends the official Gremlin.Net SDK with helper methods that simplify working with Cosmos-specific features like partition keys, automatic retries for throttled requests, and more.

For example, setting a partition key in a fluent operation is straightforward:

var g = new CosmosGraphTraversalSource(gremlinClient, new CosmosGraphTraversalSourceOptions { PartitionKey = "user-partition-key" });
var newUser = g.AddV("user").Property(T.Id, "jane-doe").Property("name", "Jane Doe").Next();

The community is active, so bugs get fixed quickly, and it’s regularly updated to align with Cosmos DB’s latest features.

Quick Tips to Avoid Headaches #

• Always match the SDK version to your Cosmos DB account’s API version to prevent compatibility gaps.
• Test small batches first to validate performance and RU usage—fluent APIs can sometimes generate more complex queries than raw strings, so it’s good to verify.
• Feel free to mix fluent and raw string queries while you transition—no need to fully switch overnight!

内容的提问来源于stack exchange，提问作者Rasmus Christensen