centrifugo-realtime

To send realtime updates from Django to frontend clients without polling, this Skill uses a Centrifugo pipeline that coordinates Django signals, transaction.on_commit, and Celery tasks to publish events via WebSocket channels.

Triggering realtime notifications on Django model save is best handled by connecting post_save signals to Celery tasks, which then publish events to Centrifugo channels only after the database transaction commits.

Yes, you can use Celery and transaction.on_commit to publish Django events to Centrifugo, ensuring realtime updates are only dispatched after the database transaction successfully commits to avoid sending stale data.

JWT authentication secures Centrifugo channel subscriptions by verifying frontend client tokens, ensuring users only receive realtime updates on channels they are authorized to access, such as user-specific notifications.

Centrifugo uses channel-based streaming for targeted realtime updates, supporting channel structures like companies:global, notifications:user#{id}, and project:{id} to route events to the correct connected frontend clients.

Your realtime Django notification fails to publish before the transaction commits because the pipeline explicitly wraps event dispatch in transaction.on_commit, preventing race conditions where clients receive updates for data not yet saved.