A single-process subscription implementation becomes insufficient when clients are distributed across multiple application instances. One server may receive an event while the interested client is connected to another server.

A shared broker such as Redis, Kafka, or another messaging system can distribute events across instances. Load balancing and connection affinity may also matter depending on the subscription architecture.