Guides

Verification Required

Message Broker Guides

Message Broker guides collect SDK examples and decision support for controlled-beta stream, replay, cursor, and queue workflows while preserving route maturity and evidence boundaries.

Current availability

Private Beta. Public beta is scheduled for .

Guide Scope

Start here when a workflow is larger than a reference snippet but not a first-success quickstart. The initial Message Broker guide publishes tested Rust SDK examples from the native API package while keeping the rendered page under reviewer acceptance.

Guide Pages

  • Available: DOCS-059

    Message Broker Rust SDK examples

    Tested Rust SDK workflows for stream publish, replay, cursor commit, shared queue processing, retry, and dead-letter handling.

  • Available: DOCS-023

    Message Broker stream and queue quickstart

    Use the local curl workflow when readers need a copy/paste first-success path before adapting SDK code.

  • Available: DOCS-032

    CLI and SDK reference

    Review lifecycle flags, diagnostics, local and remote CLI examples, release artifact commands, and Rust SDK entry points.

  • Available: DOCS-040

    Route and auth compatibility

    Check controlled-beta, verification-required, prototype, unsupported, and future boundaries before extending examples.

  • Available: DOCS-063

    Example validation

    Validate example manifests, status labels, rendered routes, evidence links, validation modes, reviewers, and limits.

Guide Guardrails

Controlled Beta Stays Visible

Message Broker examples can show tested SDK behavior while keeping route, auth, support, and replication maturity labels nearby.

Quickstart Is Separate

Use the quickstart for first-success copy/paste commands. Use guides for reusable SDK patterns and review-ready example context.

No Sensitive Output

Examples must use synthetic stream names, delivery IDs, payloads, endpoints, and groups; route operational logs and support artifacts through privacy review.