Why controllers organize request handling in Laravel - Performance Evidence

Performance: Why controllers organize request handling

MEDIUM IMPACT

This affects how efficiently the server processes requests and how quickly responses are generated, impacting server response time and user experience.

Handling HTTP requests in a Laravel app

Laravel

<?php
// app/Http/Controllers/UserController.php
namespace App\Http\Controllers;
use Illuminate\Http\Request;
use Illuminate\Support\Facades\DB;

class UserController extends Controller {
    public function index() {
        $users = DB::table('users')->get();
        return view('users.index', ['users' => $users]);
    }

    public function store(Request $request) {
        DB::table('users')->insert(['name' => $request->name]);
        return redirect('/users');
    }
}

// routes/web.php
use App\Http\Controllers\UserController;

Route::get('/users', [UserController::class, 'index']);
Route::post('/users', [UserController::class, 'store']);

Centralizes request handling in controllers, reducing code duplication and improving maintainability and server response efficiency.

📈 Performance GainReduces server processing time by avoiding repeated logic and enables better caching and optimization.

Handling HTTP requests in a Laravel app

Laravel

<?php
// routes/web.php
use Illuminate\Http\Request;
use Illuminate\Support\Facades\DB;

Route::get('/users', function () {
    $users = DB::table('users')->get();
    return view('users.index', ['users' => $users]);
});

Route::post('/users', function (Request $request) {
    DB::table('users')->insert(['name' => $request->name]);
    return redirect('/users');
});

Defining request logic directly in routes causes duplication and mixes routing with business logic, making maintenance harder and slower.

📉 Performance CostIncreases server processing time due to duplicated code and harder optimization; no caching benefits from centralized logic.

Performance Comparison

Pattern	Code Duplication	Server Processing	Maintainability	Verdict
Inline route logic	High duplication	Slower due to repeated code	Hard to maintain	[X] Bad
Controller-based handling	Low duplication	Faster with centralized logic	Easy to maintain	[OK] Good

Rendering Pipeline

When a request arrives, Laravel routes it to a controller method that handles the logic and returns a response. Controllers separate routing from business logic, streamlining request processing.

→Routing

→Controller Execution

→Response Generation

⚠️ BottleneckController Execution stage can be slow if logic is duplicated or scattered.

Core Web Vital Affected

INP

This affects how efficiently the server processes requests and how quickly responses are generated, impacting server response time and user experience.

Optimization Tips

1Use controllers to centralize request handling logic.

2Avoid placing business logic directly in route definitions.

3Centralized logic improves server response time and maintainability.

Performance Quiz - 3 Questions

Why does using controllers improve Laravel app performance?

A Because controllers centralize logic reducing duplicated code and speeding up request handling

B Because controllers automatically cache all responses

C Because controllers reduce the number of HTTP requests sent by the browser

D Because controllers load all data before routing

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and inspect server response times for requests.

What to look for: Look for lower server response times and consistent response patterns indicating efficient request handling.

Practice

1. Why do Laravel applications use controllers to handle requests instead of putting all code in routes?

easy

A. To organize code and separate routing from business logic

B. Because routes cannot handle HTTP requests

C. To make the application run faster

D. Because controllers automatically create database tables

Solution

1. Step 1: Understand the role of routes and controllers

   Routes define URL patterns, but controllers hold the logic to respond to those URLs.

2. Step 2: Recognize the benefit of separation

   Separating routing and logic keeps code organized and easier to maintain as the app grows.

3. Final Answer:

   To organize code and separate routing from business logic -> Option A

4. Quick Check:

   Controllers organize request handling = A [OK]

Hint: Controllers separate logic from routes for cleaner code [OK]

Common Mistakes:

• Thinking routes handle all logic
• Believing controllers speed up the app
• Assuming controllers create database tables

2. Which of the following is the correct way to define a controller method to handle a GET request in Laravel?

easy

A. public show() { return 'page'; }

B. public function show() { return view('page'); }

C. function show() { echo 'page'; }

D. def show() { return view('page'); }

Solution

1. Step 1: Recall Laravel controller method syntax

   Methods must be public functions inside a controller class.

2. Step 2: Check each option's syntax

   public function show() { return view('page'); } uses correct PHP syntax with public function and returns a view.

3. Final Answer:

   public function show() { return view('page'); } -> Option B

4. Quick Check:

   Laravel controller methods = public function [OK]

Hint: Use 'public function' for controller methods in Laravel [OK]

Common Mistakes:

• Omitting 'public' keyword
• Using wrong function syntax
• Using Python or other language syntax

3. Given this controller method in Laravel:

public function greet() { return 'Hello, Laravel!'; }

What will be the output when this method is called by a route?

medium

A. The view named 'Hello, Laravel!'

B. A blank page

C. An error because return type is missing

D. Hello, Laravel!

Solution

1. Step 1: Understand what the method returns

   The method returns a plain string 'Hello, Laravel!'.

2. Step 2: Know Laravel's response behavior

   Returning a string from a controller sends that string as the HTTP response body.

3. Final Answer:

   Hello, Laravel! -> Option D

4. Quick Check:

   Return string from controller = output string [OK]

Hint: Return strings directly to send text response [OK]

Common Mistakes:

• Expecting a view instead of string
• Thinking missing return type causes error
• Assuming blank page means success

4. This Laravel controller method has an error:

public function index() { echo 'Welcome'; }

What is the problem with this code?

medium

A. Using echo instead of return causes no response

B. Method must be private, not public

C. Missing semicolon after echo statement

D. Controller methods cannot output text

Solution

1. Step 1: Identify how Laravel expects responses

   Laravel expects controller methods to return responses, not echo output directly.

2. Step 2: Understand echo vs return in Laravel

   Echo sends output immediately but Laravel won't capture it as a proper HTTP response.

3. Final Answer:

   Using echo instead of return causes no response -> Option A

4. Quick Check:

   Use return, not echo, in controller methods [OK]

Hint: Always return response, never echo in controllers [OK]

Common Mistakes:

• Thinking echo works like return
• Believing method visibility is wrong
• Ignoring Laravel response rules

5. You want to organize your Laravel app so that all user-related request handling is in one place. Which approach best uses controllers to achieve this?

hard

A. Put all user logic directly inside web.php routes file

B. Create separate controllers for each user action like ShowUserController, EditUserController

C. Create a UserController with methods like show(), edit(), and update()

D. Write user logic inside middleware instead of controllers

Solution

1. Step 1: Understand controller grouping best practices

   Grouping related actions in one controller keeps code organized and easier to maintain.

2. Step 2: Evaluate options for organizing user logic

   Create a UserController with methods like show(), edit(), and update() groups user actions in UserController, which is standard Laravel practice.

3. Final Answer:

   Create a UserController with methods like show(), edit(), and update() -> Option C

4. Quick Check:

   Group related actions in one controller = B [OK]

Hint: Group related request methods in one controller class [OK]

Common Mistakes:

• Scattering user logic in routes file
• Creating too many single-action controllers
• Using middleware for business logic