Defining events in Laravel - Performance & Optimization

Performance: Defining events

MEDIUM IMPACT

This affects server-side event handling speed and how quickly the application responds to user actions or system changes.

Defining and handling events in Laravel for user actions

Laravel

<?php
namespace App\Events;

use Illuminate\Support\Facades\Mail;

class UserRegistered
{
    public $user;

    public function __construct($user)
    {
        $this->user = $user; // pass full user object
    }
}

class SendWelcomeEmail
{
    public function handle(UserRegistered $event)
    {
        Mail::to($event->user->email)->send(new WelcomeEmail($event->user));
    }
}

Passing the full user object avoids redundant database queries, reducing server load and speeding up event handling.

📈 Performance GainSingle database query per event, reducing server processing time and improving response speed.

Defining and handling events in Laravel for user actions

Laravel

<?php
namespace App\Events;

use App\Models\User;
use Illuminate\Support\Facades\Mail;

class UserRegistered
{
    public $user;

    public function __construct($user)
    {
        $this->user = $user;
    }
}

// Event listener directly queries database redundantly
class SendWelcomeEmail
{
    public function handle(UserRegistered $event)
    {
        $user = User::find($event->user->id); // redundant query
        Mail::to($user->email)->send(new WelcomeEmail($user));
    }
}

The event listener performs redundant database queries causing extra server load and slower response.

📉 Performance CostTriggers multiple database queries per event, increasing server processing time and delaying response.

Performance Comparison

Pattern	Database Queries	Server CPU Load	Response Delay	Verdict
Redundant queries in event listeners	Multiple per event	High	Increased by 100-200ms	[X] Bad
Passing full data in event object	Single per event	Low	Minimal delay	[OK] Good

Rendering Pipeline

Laravel events are processed on the server after a trigger. Efficient event definitions reduce server CPU and database load, speeding up response generation before sending HTML to the browser.

→Server Processing

→Database Queries

→Response Generation

⚠️ BottleneckDatabase queries triggered by event listeners

Optimization Tips

1Avoid redundant database queries inside event listeners.

2Pass all necessary data in event objects to reduce server load.

3Use Laravel Telescope to monitor event performance.

Performance Quiz - 3 Questions

What is a performance downside of defining Laravel events that cause redundant database queries in listeners?

A Increased server processing time and slower response

B Improved browser rendering speed

C Reduced server CPU usage

D Faster client-side JavaScript execution

DevTools: Network and Laravel Telescope

How to check: Use Laravel Telescope to monitor event listeners and database queries triggered per event. In browser DevTools Network panel, check response times for requests triggering events.

What to look for: Look for multiple database queries per event in Telescope and longer server response times in Network panel indicating inefficient event handling.