Document recommended usage patterns for creating and reusing CDP SDK clients

[simmer-rulers]

Overview

The CDP SDK requires creating a client instance, but the documentation does not clearly explain how that client should be managed across different application lifecycles.

Problem Description

Developers may be unsure whether a single client instance should be reused, recreated per request, or scoped to a specific environment. This uncertainty can lead to inefficient patterns or unnecessary complexity in real-world applications.

Expected Behavior

The documentation should clearly outline recommended client usage patterns for common environments such as long-lived services and request-based runtimes.

Proposed Solution

Add a concise documentation section describing how and when to reuse CDP SDK client instances, including basic guidance for concurrency and environment separation.

[deadenthaven86com]

No

[0xRAG]

Thanks for this documentation request! To help us prioritize and target the right content, could you share:

• SDK language: TypeScript, Python, Go, or Rust?
• SDK version you're currently using
• Your use case: Long-running server, serverless functions, CLI tool, etc.?
• Specific questions: What scenarios are you unsure about? (e.g., connection pooling, thread safety, request-scoped vs singleton clients)

This will help us create documentation that addresses real-world needs.