HotshardLearn ↗Publish / SubscribePendingIn-flightAckedDead-letter

Publish / Subscribe — pick a scenario

0/4 done

Pick one and press Start, then click Next › to step through it.

Watch for

Order M1 landing as a separate copy in both lanes, then being acked in one lane while its copy in the other lane is handled on its own.

More about this scenario
You'll learn

How a single publish fans out to an independent copy per subscription, so one event can drive many consumers with no coupling between them.

How it runs

Each PUBLISH records the message on the topic once, then the broker drops a copy into every subscription's pending queue. Billing and analytics each deliver and acknowledge their own copy of the first order.