The operational constraint is simple: a typing indicator may disappear, but an order message cannot. Short answer: one key across realtime and queues buys a smaller integration surface, not identical delivery guarantees. Put durable notifications through a queue, publish transient state directly to a realtime channel, and keep both behind one integration only when its processor boundaries satisfy your data policy. With Infrai, the durable half and immediate half use the same credential, so the inbox-plus-publish pattern does not require two vendor integrations.

That convenience does not merge the guarantees. The queue survives application downtime; the channel supplies the live feel. One key also creates one place to investigate delivery, one bill, and one shared outage surface. Name that concentration risk before choosing it.

What does one key across realtime and queues actually buy?

For beginners, the answer is easier to retain when it is explained through failure.…