Notification channels (mail, database, SMS) in Laravel - Performance & Optimization

Performance: Notification channels (mail, database, SMS)

MEDIUM IMPACT

This affects how quickly notifications are delivered and how much server and network resources are used during notification processing.

Sending notifications directly during user request

Laravel

Notification::send($user, new InvoicePaid($invoice)); // queued notifications (notification implements ShouldQueue)

Queues notifications to be processed asynchronously, freeing user request quickly.

📈 Performance GainResponse returns immediately; notification sent in background

Sending notifications directly during user request

Laravel

Notification::send($user, new InvoicePaid($invoice)); // sends mail and SMS synchronously

Sends notifications immediately during request, blocking response until delivery completes.

📉 Performance CostBlocks response for 500ms+ depending on mail/SMS provider latency

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous mail and SMS sending	0	0	0	[X] Bad
Queued mail and SMS sending	0	0	0	[OK] Good
Database notifications without indexes	0	0	0	[X] Bad
Database notifications with proper indexes	0	0	0	[OK] Good

Rendering Pipeline

Notification sending does not directly affect browser rendering but impacts server response time and perceived speed.

→Server Processing

→Network Request

→Database Operations

⚠️ BottleneckSynchronous notification sending blocks server response.

Optimization Tips

1Always queue mail and SMS notifications to avoid blocking user requests.

2Add database indexes on notification user IDs and read status for fast queries.

3Avoid sending notifications synchronously in critical user flows to improve response time.

Performance Quiz - 3 Questions

What is the main performance problem with sending notifications synchronously during a user request?

A It increases the size of the notification database

B It blocks the server response until notification delivery completes

C It causes layout shifts in the browser

D It reduces the quality of the notification content

DevTools: Network and Performance panels

How to check: Use Network panel to see request blocking time; use Performance panel to check server response time and long tasks.

What to look for: Look for long server response times caused by synchronous notification calls; check if requests return quickly when using queues.

Practice

1. In Laravel notifications, which method defines the channels a notification will be sent through?

easy

A. via

B. send

C. channels

D. notify

Solution

1. Step 1: Understand the notification class structure

   Laravel notifications use a method to specify which channels to send the notification through.

2. Step 2: Identify the method name

   The method that returns an array of channels is named via.

3. Final Answer:

   via -> Option A

4. Quick Check:

   Channel selection method = via [OK]

Hint: Remember: 'via' means 'through' which fits channel selection [OK]

Common Mistakes:

• Confusing 'send' with 'via' method
• Using 'channels' instead of 'via'
• Assuming 'notify' defines channels

2. Which of the following is the correct syntax to specify the mail channel in the via method of a Laravel notification?

easy

A. return mail();

B. return 'mail';

C. return ['mail'];

D. return ['MailChannel'];

Solution

1. Step 1: Check the return type of the via method

   The via method must return an array of channel names as strings.

2. Step 2: Identify the correct array syntax

   Returning ['mail'] is correct; returning a string or function call is incorrect.

3. Final Answer:

   return ['mail']; -> Option C

4. Quick Check:

   Channel list must be an array of strings [OK]

Hint: Always return an array of channel names in via [OK]

Common Mistakes:

• Returning a string instead of an array
• Calling a function instead of returning array
• Using incorrect channel class names

3. Given this Laravel notification code snippet, what will be stored in the database when the notification is sent?

public function toDatabase($notifiable) {
    return [
        'invoice_id' => 1234,
        'amount' => 250
    ];
}

medium

A. Only the 'invoice_id' value 1234

B. An array with keys 'invoice_id' and 'amount' and their values

C. A JSON string of the notification class name

D. An error because toDatabase must return a string

Solution

1. Step 1: Understand the toDatabase method role

   The toDatabase method returns an array of data saved in the notifications table.

2. Step 2: Analyze the returned array

   The array contains keys 'invoice_id' and 'amount' with values 1234 and 250 respectively.

3. Final Answer:

   An array with keys 'invoice_id' and 'amount' and their values -> Option B

4. Quick Check:

   toDatabase returns array data saved in DB [OK]

Hint: toDatabase returns array data stored in notifications table [OK]

Common Mistakes:

• Expecting a string instead of array
• Thinking only one key is saved
• Confusing toMail with toDatabase

4. Identify the error in this Laravel notification class snippet for sending SMS via Nexmo:

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

public function toNexmo($notifiable) {
    return (new NexmoMessage)->content('Hello!');
}

medium

A. Method name should be toSms, not toNexmo

B. The content method is not valid for NexmoMessage

C. The via method should return 'sms' instead of 'nexmo'

D. NexmoMessage class is not imported or aliased

Solution

1. Step 1: Check method names and channel names

   Using 'nexmo' in via and method toNexmo is correct for SMS via Nexmo.

2. Step 2: Verify class usage

   The NexmoMessage class must be imported with use statement or aliased; missing import causes error.

3. Final Answer:

   NexmoMessage class is not imported or aliased -> Option D

4. Quick Check:

   Missing import causes class not found error [OK]

Hint: Always import notification channel classes before use [OK]

Common Mistakes:

• Renaming toNexmo incorrectly
• Returning wrong channel name in via
• Misusing content method on NexmoMessage

5. You want to send a Laravel notification via mail, database, and SMS (Nexmo). Which of the following via method implementations correctly sets all three channels?

hard

A. return ['mail', 'database', 'nexmo'];

B. return ['mail', 'database', 'sms'];

C. return ['MailChannel', 'DatabaseChannel', 'NexmoChannel'];

D. return ['mail', 'db', 'nexmo'];

Solution

1. Step 1: Recall correct channel names for Laravel notifications

   Laravel uses lowercase strings 'mail', 'database', and 'nexmo' to specify channels.

2. Step 2: Compare options for correct channel names

   return ['mail', 'database', 'nexmo']; uses correct channel names; others use incorrect or non-existent names.

3. Final Answer:

   return ['mail', 'database', 'nexmo']; -> Option A

4. Quick Check:

   Use exact channel strings in via array [OK]

Hint: Use exact lowercase channel names: mail, database, nexmo [OK]

Common Mistakes:

• Using 'sms' instead of 'nexmo'
• Using class names instead of strings
• Using shorthand like 'db' instead of 'database'