Back to results for “Monitoring”
Redis › Keyspace Notifications

What practical use cases in a real application are well suited to keyspace notifications despite their delivery limitations?

Intermediate

Answer

Keyspace notifications work well for non critical, best effort scenarios such as triggering a cache refresh, logging activity for monitoring dashboards, sending a real time update to a connected user interface, or triggering cleanup tasks, where occasionally missing a notification would not cause serious harm to the application's correctness.
SUBSCRIBE __keyevent@0__:expired
-- Trigger a non critical UI update or cleanup task
-- when a temporary key expires
Real-world example A live dashboard displaying currently active user sessions subscribes to expired key notifications, updating the displayed count in near real time, accepting that an occasional missed notification would only cause a brief, harmless display inaccuracy.

Common follow-ups: What makes a use case appropriate versus inappropriate for this kind of best effort notification system?;How do you communicate these reliability limitations clearly to other developers on a team?