Apa iku Redis keyspace notifications?

Question

Accepted Answer

**Keyspace notifications** ngidini klien untuk subscribe (liwat Pub/Sub) menyang events babagan owah-owahan kunci — kayata kunci sing diatur, dihapus, utawa **expired**. Dheweke ngidini tumindak marang owah-owahan data ing Redis, kanthi event expiration minangka trigger sing partikular umum lan migunani. ## Enabling lan subscribing ```bash # keyspace notifications are OFF by default — enable the event classes you want CONFIG SET notify-keyspace-events KEA # K=keyspace, E=keyevent, A=all event types # subscribe to events: e.g. all expirations across the database PSUBSCRIBE "__keyevent@0__:expired" # fires when ANY key expires (with the key name) PSUBSCRIBE "__keyspace@0__:mykey" # all events on a specific key ``` Kowe enable notifications (`notify-keyspace-events`, milih events endi wae) lan subscribe menyang channel spesial: `__keyevent@__:` (events saka tipe, contone `expired`, kanthi kunci sing kena pengaruh) utawa `__keyspace@__:` (events ing kunci spesifik). ## The expiration event: pola umum ```text The "expired" event is widely used as a TIMER/SCHEDULER: → set a key with a TTL; when it expires, you get notified → trigger an action → e.g. "order:123:hold" expires in 15 min → notification → release the held inventory → delayed jobs, session-expiry handling, scheduled actions without a separate scheduler ``` ## Important caveats ```text ⚠️ Built on PUB/SUB → fire-and-forget: if no subscriber is connected when the event fires, it's MISSED (not reliable/persistent). Don't rely on it for critical events. ⚠️ "expired" fires when the key is actually REMOVED (lazy/active expiration), which can LAG behind the exact TTL time → not precise timing. ⚠️ Has overhead at high volume; for reliable event handling, use STREAMS instead. ``` ## Mengapa iki penting Pamahaman babagan keyspace notifications minangka pangertian sing migunani kanggo **tumindak marang owah-owahan data ing Redis**, kemampuan sing ngidini pola-pola tertentu sing didorong acara — sanajan pamahaman babagan keterbatasane uga penting. Fitur iki ngidini klien **subscribe menyang events babagan owah-owahan kunci** (sets, deletes, lan utamane **expirations**) liwat Pub/Sub, ngidini Redis kanggo kasihake kabar menyang aplikasi nalika data owah. **Expiration event utamane** ndukung pola umum lan elegan: nggunakake TTL kunci minangka **timer/scheduler** — atur kunci kanggo expired sawise sawetara delay, lan notifikasi expiration ngaktifake aksi (nglilisake inventory sing didandani sawise periode tahan, nangani expiry session, njalanake delayed jobs), nyedhiyakake kelakuan tindakan terjadwal tanpa sistem scheduling terpisah. Pamahaman carane enable notifications (`notify-keyspace-events`) lan subscribe menyang channel keyevent/keyspace spesial minangka mekanisme praktis. Kritis, pamahaman babagan **caveats** penting kanggo nggunakake iki kanthi bener: amarga iku dibangun ing **Pub/Sub, iku fire-and-forget** (events tanpa subscriber sing koneksi permanen ilang — mula iku ora bisa dipercaya kanggo events kritis), **expired event lags** TTL tepat (ngasiking nalika kunci bener-bener dihapus dening lazy/active expiration, mula timing ora tepat), lan wae overhead ing volume dhuwur — tegesane kanggo reliable event handling, Streams utawa mekanisme liya luwih apik. Sadaran iki nyegah over-relying ing notifications kanggo guaranteed delivery. Samesthengga tumindak marang owah-owahan data Redis (utamane expirations minangka timers) minangka pola migunani kanggo delayed actions lan scheduling, lan samesthengga keyspace notifications nyedhiyakake iku nanging kanthi keterbatasan reliability lan timing penting (inherit fire-and-forget nature Pub/Sub), pamahaman keyspace notifications — apa iki, pola expiration-as-timer, lan utamane caveats — minangka pangertian migunani lan relevan praktis kanggo nggunakake fitur iki kanthi bener sanajan ngerti nalika keterbatasane mbutuhake pendekatan luwih bisa dipercaya.