Queued notifications in Laravel - Performance & Optimization

Performance: Queued notifications

HIGH IMPACT

This affects how quickly the page responds to user actions by offloading notification sending to background jobs, improving interaction speed.

Sending notifications after user actions without blocking the UI

Laravel

Notification::send($user, (new InvoicePaid($invoice))->delay(now()->addSeconds(5)));
// or using ShouldQueue interface on notification class
$user->notify((new InvoicePaid($invoice))->delay(now()->addSeconds(5)));

Queues the notification to be processed in the background, freeing the request to respond immediately.

📈 Performance GainNon-blocking request, reduces INP by offloading work to queue workers.

Sending notifications after user actions without blocking the UI

Laravel

Notification::send($user, new InvoicePaid($invoice));

Sends notification synchronously, blocking the request until sending completes.

📉 Performance CostBlocks rendering and user interaction for the duration of notification sending, increasing INP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous notification sending	N/A	N/A	Blocks server response delaying paint	[X] Bad
Queued notification sending	N/A	N/A	Server responds immediately, faster paint and interaction	[OK] Good

Rendering Pipeline

Synchronous notification sending blocks the server response, delaying browser rendering and interaction readiness. Queued notifications defer this work to background processes, allowing the server to send the response faster and the browser to paint and become interactive sooner.

→Server Response Time

→Interaction Readiness

⚠️ BottleneckServer blocking on notification sending delays response and increases INP.

Core Web Vital Affected

INP

This affects how quickly the page responds to user actions by offloading notification sending to background jobs, improving interaction speed.

Optimization Tips

1Always implement notifications with Laravel's ShouldQueue interface to send asynchronously.

2Avoid sending notifications directly during HTTP requests to prevent blocking response.

3Use queue workers to handle notification jobs in the background for better user experience.

Performance Quiz - 3 Questions

What is the main performance benefit of using queued notifications in Laravel?

A They reduce the size of notification payloads sent to users.

B They allow the server to respond faster by sending notifications asynchronously.

C They improve the visual layout stability of the page.

D They increase the number of DOM nodes for notifications.

DevTools: Performance

How to check: Record a performance profile while triggering a notification. Look for long server response times or blocking scripts.

What to look for: Long tasks blocking main thread or delayed server response indicate synchronous notification sending.

Practice

1. What is the main benefit of using queued notifications in Laravel?

easy

A. They automatically retry failed notifications indefinitely.

B. They allow notifications to be sent only during business hours.

C. They send messages without slowing down your app.

D. They encrypt notification content for security.

Solution

1. Step 1: Understand queued notifications purpose

   Queued notifications delay sending to avoid blocking app processes.

2. Step 2: Identify the main benefit

   This means the app stays fast because sending happens in the background.

3. Final Answer:

   They send messages without slowing down your app. -> Option C

4. Quick Check:

   Queued notifications improve app speed = B [OK]

Hint: Queued notifications run in background to keep app fast [OK]

Common Mistakes:

• Thinking queued notifications encrypt messages
• Assuming they only send during specific hours
• Believing they retry indefinitely without limits

2. Which interface must a Laravel notification implement to be queued?

easy

A. QueueInterface

B. Queueable

C. ShouldNotify

D. ShouldQueue

Solution

1. Step 1: Recall Laravel notification queue setup

   Notifications must implement the ShouldQueue interface to be queued.

2. Step 2: Differentiate interface and trait

   Queueable is a trait to help with queue features, not an interface.

3. Final Answer:

   ShouldQueue -> Option D

4. Quick Check:

   Implement ShouldQueue to queue notifications = A [OK]

Hint: Implement ShouldQueue interface to queue notifications [OK]

Common Mistakes:

• Confusing Queueable trait with interface
• Using non-existent interfaces like ShouldNotify
• Assuming QueueInterface is required

3. Given this notification class snippet, what will happen when notify() is called?

use Illuminate\Notifications\Notification;
use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;

class InvoicePaid extends Notification implements ShouldQueue
{
    use Queueable;

    public function via($notifiable)
    {
        return ['mail'];
    }

    public function toMail($notifiable)
    {
        return (new MailMessage)->line('Invoice paid.');
    }
}

medium

A. The notification will be sent immediately without queuing.

B. The notification will be queued and sent asynchronously.

C. The notification will fail because Queueable trait is missing.

D. The notification will send via SMS instead of mail.

Solution

1. Step 1: Check if notification implements ShouldQueue

   The class implements ShouldQueue, so it will be queued.

2. Step 2: Confirm use of Queueable trait and mail channel

   Queueable trait is used, and via() returns 'mail', so mail will be sent asynchronously.

3. Final Answer:

   The notification will be queued and sent asynchronously. -> Option B

4. Quick Check:

   ShouldQueue + Queueable = queued notification = D [OK]

Hint: Implement ShouldQueue and use Queueable to queue notifications [OK]

Common Mistakes:

• Assuming Queueable trait is optional
• Thinking notification sends immediately despite ShouldQueue
• Confusing mail channel with SMS

4. What is wrong with this notification class if it does not queue as expected?

use Illuminate\Notifications\Notification;
use Illuminate\Bus\Queueable;

class OrderShipped extends Notification
{
    use Queueable;

    public function via($notifiable)
    {
        return ['mail'];
    }

    public function toMail($notifiable)
    {
        return (new MailMessage)->line('Order shipped.');
    }
}

medium

A. It is missing the ShouldQueue interface implementation.

B. The Queueable trait should not be used here.

C. The via() method must return 'database' to queue notifications.

D. The toMail() method must be named toQueuedMail() to queue.

Solution

1. Step 1: Check interface implementation for queuing

   The class uses Queueable trait but does not implement ShouldQueue interface.

2. Step 2: Understand queuing requirements

   Without ShouldQueue, Laravel sends notification immediately, ignoring queue.

3. Final Answer:

   It is missing the ShouldQueue interface implementation. -> Option A

4. Quick Check:

   Must implement ShouldQueue to queue notifications = A [OK]

Hint: Implement ShouldQueue interface to enable queuing [OK]

Common Mistakes:

• Thinking Queueable trait alone queues notifications
• Believing via() channel affects queuing
• Renaming toMail() method incorrectly

5. You want to send a notification that queues and retries up to 3 times if it fails. Which code snippet correctly sets this up? A)

class PaymentFailed extends Notification implements ShouldQueue
{
    use Queueable;

    public $tries = 3;

    public function via($notifiable) { return ['mail']; }
}

B)

class PaymentFailed extends Notification implements ShouldQueue
{
    use Queueable;

    public function via($notifiable) { return ['mail']; }

    public function retryTimes() { return 3; }
}

C)

class PaymentFailed extends Notification
{
    use Queueable;

    public $tries = 3;

    public function via($notifiable) { return ['mail']; }
}

D)

class PaymentFailed extends Notification implements ShouldQueue
{
    use Queueable;

    public function via($notifiable) { return ['mail']; }

    public $maxRetries = 3;
}

hard

A. Correctly sets retry attempts with public $tries property.

B. Uses retryTimes() method which Laravel does not recognize.

C. Missing ShouldQueue interface, so notification won't queue.

D. Uses $maxRetries property which is not used by Laravel.

Solution

1. Step 1: Identify queuing and retry setup

   Laravel uses public $tries property to set retry attempts on queued jobs/notifications.

2. Step 2: Check interface and property correctness

   Correctly sets retry attempts with public $tries property. implements ShouldQueue and sets public $tries = 3 correctly.

3. Final Answer:

   Correctly sets retry attempts with public $tries property. -> Option A

4. Quick Check:

   Use public $tries for retries in queued notifications = A [OK]

Hint: Set public $tries = 3 and implement ShouldQueue to retry [OK]

Common Mistakes:

• Using non-existent retryTimes() method
• Forgetting to implement ShouldQueue interface
• Using wrong property name like $maxRetries