Skip to content
ParticleDB
Release candidateParticleDB 1.1.19-rc.17 is not yet GA or ready for production data.Release status →

Change notifications

Notifications and durable change feeds solve different problems. A connected client receiving an event does not establish replay after a disconnect.

Verify that your release supports the intended subscription command or streaming endpoint. Check authentication, ordering, reconnection behavior, buffering and backpressure.

Record pending work in a table as part of the application transaction. A worker can read that state and update its progress. Use stable identifiers and explicit retry handling.

Do not describe a transient notification as a durable queue or promise that a disconnected consumer receives every event.

Agent and workflow patterns · Transactions

Documentation home · Troubleshooting