Model events and observers in Laravel - Performance & Optimization

Performance: Model events and observers

MEDIUM IMPACT

This affects the server-side response time and indirectly impacts client perceived speed by adding processing before or after database operations.

Handling model lifecycle logic such as logging or notifications

Laravel

class UserObserver {
  public function created(User $user) {
    Log::info('User created: ' . $user->id);
    Notification::send($user, new WelcomeNotification());
  }
}

// In AppServiceProvider boot method
User::observe(UserObserver::class);

Separates side effects from controller, allowing Laravel to handle them asynchronously or deferred if configured.

📈 Performance GainReduces controller response time by 50-100ms and centralizes logic for easier maintenance.

Handling model lifecycle logic such as logging or notifications

Laravel

public function store(Request $request) {
  $user = User::create($request->all());
  // Logging directly in controller
  Log::info('User created: ' . $user->id);
  // Sending notification directly
  Notification::send($user, new WelcomeNotification());
  return redirect()->back();
}

Mixing side effects in controller increases response time and duplicates code if used in multiple places.

📉 Performance CostBlocks response until all side effects complete, increasing server response time by 50-100ms depending on tasks.

Performance Comparison

Pattern	Server Processing	Database Calls	Response Time Impact	Verdict
Side effects in controller	High (mixed logic)	Normal	Increases by 50-100ms	[X] Bad
Using model observers	Moderate (centralized)	Normal	Minimal if synchronous	[!] OK
Observers with queued jobs	Low (async)	Normal	Minimal, non-blocking	[OK] Good

Rendering Pipeline

Model events and observers run on the server before sending the response. They do not affect browser rendering directly but impact server response time.

→Server Processing

→Database Interaction

⚠️ BottleneckServer Processing due to synchronous event handling

Optimization Tips

1Keep model event logic lightweight to avoid blocking server response.

2Use queued jobs for heavy or slow tasks triggered by observers.

3Centralize side effects in observers instead of controllers for maintainability and performance.

Performance Quiz - 3 Questions

What is the main performance impact of using model observers in Laravel?

A They increase server response time by adding processing before/after database actions.

B They slow down browser rendering by adding extra DOM nodes.

C They increase CSS calculation time on the client.

D They add extra JavaScript bundle size.

DevTools: Network

How to check: Open DevTools Network tab, record a request that triggers model events, check server response time in the timing breakdown.

What to look for: Look for longer server response times indicating blocking operations in model events or observers.

Practice

1. What is the main purpose of model events in Laravel?

easy

A. To react automatically when a model is created, updated, or deleted

B. To define database table relationships

C. To create database migrations

D. To write raw SQL queries

Solution

1. Step 1: Understand model events

   Model events are hooks that trigger when a model changes, like creation or deletion.

2. Step 2: Identify their purpose

   They let you run code automatically on these changes, such as logging or notifications.

3. Final Answer:

   To react automatically when a model is created, updated, or deleted -> Option A

4. Quick Check:

   Model events = react on model changes [OK]

Hint: Model events trigger on data changes automatically [OK]

Common Mistakes:

• Confusing events with database migrations
• Thinking events define relationships
• Assuming events run SQL queries directly

2. Which of the following is the correct way to register an observer for a model in Laravel?

easy

A. User::addObserver('UserObserver');

B. User::observe(UserObserver::class);

C. User::registerObserver(UserObserver);

D. User::attachObserver(UserObserver::class);

Solution

1. Step 1: Recall observer registration syntax

   Laravel uses the static method observe() on the model to register observers.

2. Step 2: Match correct syntax

   The correct syntax is Model::observe(ObserverClass::class); which matches User::observe(UserObserver::class);.

3. Final Answer:

   User::observe(UserObserver::class); -> Option B

4. Quick Check:

   Register observer = observe() method [OK]

Hint: Use observe() method with ::class for observers [OK]

Common Mistakes:

• Using wrong method names like registerObserver
• Passing observer as string instead of ::class
• Confusing attachObserver with observe

3. Given this observer method in Laravel:

public function created(User $user) {
    Log::info('User created: ' . $user->id);
}

What happens when a new User model is saved?

medium

A. An error is thrown because created() is invalid

B. The user is deleted immediately

C. Nothing happens automatically

D. A log entry with the new user's ID is created

Solution

1. Step 1: Understand the created() observer method

   The created() method runs after a model is saved for the first time.

2. Step 2: Analyze the method body

   It logs info with the new user's ID, so a log entry is made.

3. Final Answer:

   A log entry with the new user's ID is created -> Option D

4. Quick Check:

   created() logs user ID after save [OK]

Hint: created() runs after first save, logs info [OK]

Common Mistakes:

• Thinking created() deletes the model
• Assuming created() does nothing
• Confusing created() with invalid method

4. What is wrong with this observer registration code?

public function boot() {
    User::observe();
}

medium

A. The observe() method is called without passing the observer class

B. The boot() method should be named bootObserver()

C. User model cannot have observers

D. The observe() method should be called on the observer class

Solution

1. Step 1: Check observe() method usage

   observe() requires the observer class as an argument to register it.

2. Step 2: Identify missing argument

   Here, observe() is called with no arguments, so it will cause an error.

3. Final Answer:

   The observe() method is called without passing the observer class -> Option A

4. Quick Check:

   observe() needs observer class argument [OK]

Hint: Always pass observer class to observe() [OK]

Common Mistakes:

• Calling observe() without arguments
• Renaming boot() incorrectly
• Calling observe() on wrong class

5. You want to log a message every time a Post model is updated, but only if the title has changed. How should you implement this in a PostObserver?

hard

A. Use the deleted(Post $post) method and check if $post->isDirty('title') is true

B. Use the saving(Post $post) method and check if $post->wasChanged('title') is true

C. Use the updated(Post $post) method and check if $post->wasChanged('title') is true

D. Use the created(Post $post) method and check if $post->title is not empty

Solution

1. Step 1: Identify correct event for update

   The updated() method runs after a model is updated, suitable for this task.

2. Step 2: Check how to detect changed attributes

   wasChanged('title') returns true if the title attribute was changed during the update.

3. Step 3: Combine logic

   Inside updated(), check wasChanged('title') to log only when title changed.

4. Final Answer:

   Use the updated(Post $post) method and check if $post->wasChanged('title') is true -> Option C

5. Quick Check:

   updated() + wasChanged('title') detects title changes [OK]

Hint: Use updated() and wasChanged() to detect attribute changes [OK]

Common Mistakes:

• Using created() or deleted() for updates
• Using wasChanged() inside saving() which runs before update
• Checking isDirty() in deleted() event