Email Queue Architecture in Senddera

Why Use Queues?

Sending thousands of emails simultaneously is resource-intensive. If Senddera tried to send each email during the web request, your browser would time out. Queues allow the application to offload this work to background processes.

The Stack

Senddera uses a multi-layered queue architecture built on top of Laravel:

• Redis (Recommended): An in-memory data structure store used as the primary queue driver for maximum performance.
• Queue Workers: Dedicated background processes that listen for new jobs and execute them.
• Supervisor: A process monitor that ensures your queue workers are always running and restarts them if they fail.

Queue Priority

Not all emails are created equal. Senddera uses multiple queues to prioritize different types of messages:

• High Priority: Password resets, double opt-in confirmations, and other transactional emails.
• Default: Standard campaign sends.
• Low Priority: Maintenance tasks and report generation.

Handling Failures

If a sending service is temporarily down, Senddera doesn't just give up. It implements an exponential backoff strategy, automatically retrying failed jobs with increasing delays until they succeed or reach the maximum retry limit.