You need to broadcast live pricing updates from your service to tens of thousands of connected clients. Clients that disconnect temporarily do not need to receive missed messages. Which approach should you use with Azure Cache for Redis?

The correct approach is to use Redis Pub/Sub channels. Pub/Sub is designed for broadcasting messages to multiple subscribers without guaranteeing delivery to disconnected clients, which aligns perfectly with the requirement that missed messages are not needed. Publishers send messages to a channel, and subscribers receive messages published to that channel. Redis Streams with consumer groups would queue messages for disconnected clients, which is explicitly not required. Keyspace notifications are for monitoring changes to Redis keys, not for broadcasting live updates. AOF persistence saves the Redis dataset to disk for durability and recovery, but it does not queue or replay published Pub/Sub messages to reconnecting clients.