Tutorials

Combine identity, Channels, messages, conversations, and scale boundaries into deployable product flows.

Scenario tutorials begin with a product outcome and connect the product service, client SDK, and WuKongIM cluster into one end-to-end path. They are not exhaustive API references; they establish responsibilities, ordering, success criteria, and compensation boundaries.

Establish a trusted boundary first

HTTP commands in these tutorials are for local development or a trusted product service. Current product HTTP routes have no general product-authentication middleware. Browsers and mobile clients must not hold these management capabilities directly.

Direct Chat

Connect identity, person-Channel messaging, offline recovery, unread state, and multi-device verification.

Groups & Large Groups

Connect group membership, group messages, churn, and 100,000-member capacity boundaries.

Message Push

Build recoverable notifications with offline webhooks, a product outbox, and providers.

AI & IoT Communication

Combine AI stream projections, telemetry, durable commands, and business receipts.

Choose a path

Goal	Start here	Most important boundary
Two users exchange messages	Direct Chat	Use the peer UID; the server derives the canonical person Channel
Ordinary group chat	Groups & Large Groups	The product owns group lifecycle and membership; WuKongIM owns the message log
A 100,000-member community or room	Groups & Large Groups	Batched reconciliation, paged post-commit fanout, and hotspot capacity testing
Offline mobile notification	Message Push	The webhook produces candidates; the product outbox and provider receipts own reliability
Streaming AI answer	AI & IoT Communication	Commit the base first, persist terminal projection, and keep live token streaming product-owned
Device telemetry and control	AI & IoT Communication	A command-sync cursor is not proof of business execution

Shared success model

product authorization / membership state
        |
        v
SDK SEND or trusted HTTP send
        -> Channel quorum commit -> SENDACK / reason=1
        -> online delivery / webhook / plugin
        -> reconnect sync from the durable log

Treat “message committed,” “one Session received online delivery,” “the user's unread projection changed,” and “the business action completed” as four different outcomes. Strong business consistency belongs in the product service with its database, idempotency keys, and compensation workflow.

All four scenario tutorials are now published. Continue with Use Cases, Integration Architecture, and Messaging to turn these examples into your own product protocol and reliability targets.