Terminable middleware in Laravel - Performance & Optimization

Performance: Terminable middleware

MEDIUM IMPACT

Terminable middleware affects the response lifecycle by running code after the response is sent, impacting server response time and user experience.

Running cleanup or logging tasks after sending the HTTP response

Laravel

<?php
namespace App\Http\Middleware;
use Closure;
class LogMiddleware {
    public function handle($request, Closure $next) {
        return $next($request);
    }
    public function terminate($request, $response) {
        // Logging happens after response sent
        \Log::info('Request logged');
    }
}

Terminable middleware runs logging after response, so user gets response faster and logging does not delay interaction.

📈 Performance GainResponse sent immediately; logging runs after response, improving INP and perceived speed.

Running cleanup or logging tasks after sending the HTTP response

Laravel

<?php
namespace App\Http\Middleware;
use Closure;
class LogMiddleware {
    public function handle($request, Closure $next) {
        $response = $next($request);
        // Logging happens here before response is sent
        \Log::info('Request logged');
        return $response;
    }
}

Logging blocks the response until finished, increasing server response time and delaying user interaction.

📉 Performance CostBlocks response for logging duration, increasing Time to Interactive (TTI) and INP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Logging inside handle()	0 (server-side)	0	0	[X] Bad - blocks response, delays user interaction
Logging inside terminate()	0 (server-side)	0	0	[OK] Good - response sent immediately, no delay

Rendering Pipeline

Terminable middleware runs after the HTTP response is sent to the browser, so it does not block rendering or painting stages.

→Server Response

→Post-Response Processing

⚠️ BottleneckServer Response blocking due to synchronous tasks in middleware handle method

Core Web Vital Affected

INP

Terminable middleware affects the response lifecycle by running code after the response is sent, impacting server response time and user experience.

Optimization Tips

1Put long-running tasks like logging or cleanup in the terminate() method.

2Avoid blocking the response in the handle() method to improve user experience.

3Use terminable middleware to keep server response fast and interaction smooth.

Performance Quiz - 3 Questions

What is the main performance benefit of using terminable middleware in Laravel?

A It runs tasks after the response is sent, reducing user wait time.

B It caches the entire response to speed up future requests.

C It compresses the response to reduce download size.

D It delays the response until all tasks finish.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check Time to First Byte (TTFB) and response time for requests.

What to look for: Long TTFB or delayed response indicates blocking middleware; fast response with background tasks after indicates terminable middleware use.

Practice

1. What is the main purpose of terminable middleware in Laravel?

easy

A. To validate user input before processing

B. To modify the HTTP request before it reaches the controller

C. To handle database migrations automatically

D. To run code after the HTTP response has been sent to the user

Solution

1. Step 1: Understand middleware timing

   Terminable middleware runs after the response is sent, unlike regular middleware that runs before.

2. Step 2: Identify terminable middleware purpose

   It is used for tasks like logging or cleanup after response delivery.

3. Final Answer:

   To run code after the HTTP response has been sent to the user -> Option D

4. Quick Check:

   Terminable middleware = post-response code [OK]

Hint: Terminable middleware runs after response is sent [OK]

Common Mistakes:

• Confusing terminable middleware with regular middleware
• Thinking it runs before the controller
• Assuming it handles request validation

2. Which method must be implemented in a Laravel terminable middleware class?

easy

A. handle

B. process

C. terminate

D. finish

Solution

1. Step 1: Recall terminable middleware interface

   Terminable middleware requires a terminate method to run code after response.

2. Step 2: Differentiate from handle method

   handle runs before response, terminate runs after.

3. Final Answer:

   terminate -> Option C

4. Quick Check:

   Post-response method = terminate [OK]

Hint: Terminate method runs after response in terminable middleware [OK]

Common Mistakes:

• Using handle instead of terminate for post-response code
• Assuming process or finish are valid methods
• Not implementing terminate method at all

3. Given this terminable middleware code, what will be logged after the response is sent?

class LogAfterResponse {
    public function handle($request, Closure $next) {
        return $next($request);
    }
    public function terminate($request, $response) {
        Log::info('Response sent with status: ' . $response->status());
    }
}

medium

A. Logs the request URL before sending the response

B. Logs the response status code after sending the response

C. Throws an error because terminate method is missing parameters

D. Does nothing because terminate is not called automatically

Solution

1. Step 1: Analyze handle method

   The handle method passes the request to next middleware/controller without changes.

2. Step 2: Analyze terminate method

   After response is sent, terminate logs the response status code using Log::info.

3. Final Answer:

   Logs the response status code after sending the response -> Option B

4. Quick Check:

   terminate logs status post-response [OK]

Hint: Terminate runs after response, so logs status then [OK]

Common Mistakes:

• Thinking terminate runs before response
• Assuming terminate is not called automatically
• Confusing request and response parameters

4. Identify the error in this terminable middleware code:

class CleanupMiddleware {
    public function handle($request, Closure $next) {
        return $next($request);
    }
    public function terminate() {
        // cleanup code here
    }
}

medium

A. terminate method must accept $request and $response parameters

B. handle method must return a string, not a response

C. terminate method should be named handleTerminate

D. handle method must not call $next

Solution

1. Step 1: Check terminate method signature

   Terminable middleware's terminate method must accept both $request and $response parameters.

2. Step 2: Identify missing parameters

   The code's terminate method has no parameters, which will cause errors.

3. Final Answer:

   terminate method must accept $request and $response parameters -> Option A

4. Quick Check:

   terminate signature requires request and response [OK]

Hint: Terminate method needs both request and response parameters [OK]

Common Mistakes:

• Omitting parameters in terminate method
• Renaming terminate method incorrectly
• Misunderstanding handle method return type

5. You want to log the total time taken to process a request including after the response is sent. How would you implement this using terminable middleware?

class RequestTimer {
    protected $startTime;

    public function handle($request, Closure $next) {
        $this->startTime = microtime(true);
        return $next($request);
    }

    public function terminate($request, $response) {
        // What code should go here?
    }
}

hard

A. $duration = microtime(true) - $this->startTime;
\Log::info('Request took ' . $duration . ' seconds');

B. $duration = microtime(true) + $this->startTime;
\Log::info('Request took ' . $duration . ' seconds');

C. return $this->startTime; // terminate must return a value

D. Call $this->handle($request, $next) again inside terminate

Solution

1. Step 1: Calculate duration in terminate method

   Use current time minus stored start time to get total duration.

2. Step 2: Log the duration

   Use Log::info to record the time taken after response is sent.

3. Final Answer:

   $duration = microtime(true) - $this->startTime; \Log::info('Request took ' . $duration . ' seconds'); -> Option A

4. Quick Check:

   Duration = now - startTime, then log [OK]

Hint: Subtract start time from current time in terminate to get duration [OK]

Common Mistakes:

• Adding times instead of subtracting
• Returning values from terminate method
• Calling handle method inside terminate