jobs-and-notifications

To send email and database notifications in the background, defer the task using queued dispatch, route messages per-user via Notifiable implementations, and deliver across configured channels like in-app inbox and WebSocket.

Background jobs handle deferred work units like report generation to keep request paths responsive, while user notifications route recipient-facing messages across email, database inbox, and WebSocket channels.

Keep API requests responsive by deferring heavy tasks like image processing to background job workers using async queued dispatch, separating long-running execution from the immediate request path.

Yes, you can broadcast real-time WebSocket messages alongside email and in-app database inbox delivery by rendering multiple channels within a single notification dispatched to specific recipients.

Yes, the system provides explicit guidance on retry and timeout configurations for queued dispatch, ensuring background jobs and notifications handle failures gracefully without blocking the main execution.

Use sync dispatch for immediate message delivery when latency is acceptable, and switch to queued dispatch for background work or multi-channel notifications to avoid blocking the request path.