Direct Mode Support for the Rust SDK

[tedli-cmd]

Feature Summary

Direct Mode Support for the Rust SDK

Feature Description

Reason
We are migrating some low‑latency Java services to Rust. The Java SDK’s Direct Mode is essential for meeting our performance requirements, and Gateway Mode alone adds too much latency for our workload.

Request
Please consider adding Direct Mode transport (TCP, address cache, partition routing, and a mode selector). Even a minimal initial version would be extremely helpful.

We would be happy to provide workload details or help test early builds. Thank you for considering this enhancement.

Use Case

No response

Alternatives

No response

Additional Context

No response

[github-actions]

Thank you for your feedback. Tagging and routing to the team members best able to assist. cc @Pilchie

Generated by Agentic Triage for issue #4523 · ● 2M · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@8e6d7c86bba37371d2d0eee1a23563db3e561eb5

[github-actions]

🎯 Agentic Issue Triage

Summary: The author requests Direct Mode transport support (TCP, address cache, partition routing) for the Cosmos DB Rust SDK, citing latency requirements when migrating low-latency Java services to Rust where Gateway Mode is insufficient.

📋 Issue Details

• Crate / module: sdk/cosmos/
• Affected API: Transport layer / connection mode configuration
• Scenario: Migrating latency-sensitive Java services to Rust; existing Java SDK Direct Mode is needed to meet performance SLAs
• Root ask: Add Direct Mode (TCP transport, address cache, partition routing, mode selector) to the Cosmos Rust SDK

🔎 Debugging / Reproduction Notes

This is a feature request, not a bug. There is no reproduction case, but the author notes they can provide workload details or assist with testing early builds.

Suggested investigation steps:

1. Review the current Cosmos Rust SDK transport layer to understand what modes are already supported.
2. Evaluate the Java SDK's Direct Mode implementation as a reference for required components (TCP transport, address cache, partition routing).
3. Assess feasibility of a minimal initial implementation and define a roadmap.

🏷️ Label Confidence

• Category: Client — The request targets the sdk/cosmos/ crate which does not begin with azure_resourcemanager_, so it is a Client library.
• Service: Cosmos — The issue explicitly refers to the Cosmos DB SDK and its Direct Mode feature.
• Confidence: High — The issue unambiguously references a specific SDK crate and Azure service with no ambiguity.

👥 Owner Routing

• Matched CODEOWNERS entry: # ServiceLabel: %Cosmos — the predicted service label Cosmos matches this entry.
• AzureSDKOwners: none listed
• ServiceOwners: @Pilchie
• Routing action: Added Service Attention and needs-team-attention labels; left unassigned per routing rules for ServiceOwners-only entries.

Generated by Agentic Triage for issue #4523 · ● 2M · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@8e6d7c86bba37371d2d0eee1a23563db3e561eb5