Resource controllers in Laravel - Performance & Optimization

Performance: Resource controllers

MEDIUM IMPACT

Resource controllers affect server response time and client load speed by organizing route handling efficiently.

Handling CRUD routes in a Laravel application

Laravel

Route::resource('posts', PostController::class);

Registers all CRUD routes in one call, optimizing route matching and reducing server processing overhead.

📈 Performance GainSingle route registration reduces route lookup time and improves server response speed.

Handling CRUD routes in a Laravel application

Laravel

Route::get('/posts', [PostController::class, 'index']);
Route::post('/posts', [PostController::class, 'store']);
Route::get('/posts/create', [PostController::class, 'create']);
Route::get('/posts/{id}', [PostController::class, 'show']);
Route::put('/posts/{id}', [PostController::class, 'update']);
Route::delete('/posts/{id}', [PostController::class, 'destroy']);

Defining each route manually increases route registration time and can cause slower route matching.

📉 Performance CostAdds multiple route lookups increasing server response time slightly for each request.

Performance Comparison

Pattern	Route Definitions	Route Matching Cost	Server Response Time	Verdict
Manual route definitions for each CRUD action	Multiple lines	Multiple lookups per request	Higher due to overhead	[X] Bad
Single resource controller route	One line	Single lookup per request	Lower due to optimized matching	[OK] Good

Rendering Pipeline

Resource controllers streamline backend route handling, reducing server processing before sending HTML to the browser.

→Server Routing

→Response Generation

⚠️ BottleneckRoute matching and controller method dispatch

Core Web Vital Affected

LCP

Resource controllers affect server response time and client load speed by organizing route handling efficiently.

Optimization Tips

1Use Route::resource to register all CRUD routes in one call.

2Avoid defining each CRUD route manually to reduce route matching overhead.

3Efficient routing improves server response time and helps faster page load.

Performance Quiz - 3 Questions

How does using a resource controller in Laravel affect server response time?

A It increases server response time by adding more routes.

B It reduces route matching time by grouping routes efficiently.

C It has no effect on server response time.

D It slows down the database queries.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the server response time for routes.

What to look for: Look for faster response times and fewer route-related delays indicating efficient routing.

Practice

1. What is the main purpose of a resource controller in Laravel?

easy

A. To create views without a controller

B. To handle database migrations automatically

C. To group all CRUD actions for a resource in one controller

D. To manage user authentication only

Solution

1. Step 1: Understand what resource controllers do

   Resource controllers in Laravel group related actions like create, read, update, and delete (CRUD) for a resource in one controller class.

2. Step 2: Compare options with this definition

   Only To group all CRUD actions for a resource in one controller correctly describes this grouping of CRUD actions. Other options describe unrelated features.

3. Final Answer:

   To group all CRUD actions for a resource in one controller -> Option C

4. Quick Check:

   Resource controller = CRUD grouping [OK]

Hint: Resource controllers group CRUD actions in one place [OK]

Common Mistakes:

• Confusing resource controllers with migrations
• Thinking resource controllers handle views alone
• Assuming resource controllers manage authentication

2. Which of the following is the correct syntax to register a resource controller named PostController for the route /posts?

easy

A. Route::resource('posts', PostController::class);

B. Route::controller('posts', PostController::class);

C. Route::get('posts', PostController::resource());

D. Route::resource('PostController', 'posts');

Solution

1. Step 1: Recall Laravel resource route syntax

   The correct syntax uses Route::resource('uri', ControllerClass::class) to register all resource routes.

2. Step 2: Check each option

   Route::resource('posts', PostController::class); matches the correct syntax. Route::controller('posts', PostController::class); uses controller which is different. Route::get('posts', PostController::resource()); is invalid syntax. Route::resource('PostController', 'posts'); swaps parameters incorrectly.

3. Final Answer:

   Route::resource('posts', PostController::class); -> Option A

4. Quick Check:

   Resource route syntax = Route::resource(uri, Controller::class) [OK]

Hint: Use Route::resource('uri', Controller::class) to register resource routes [OK]

Common Mistakes:

• Using Route::controller instead of Route::resource
• Swapping URI and controller parameters
• Calling resource() as a method on controller instance

3. Given this resource controller route registration:
Route::resource('photos', PhotoController::class);
Which URL and HTTP method will call the destroy method in PhotoController for photo with ID 5?

medium

A. PUT /photos/5/destroy

B. GET /photos/5/destroy

C. POST /photos/5/delete

D. DELETE /photos/5

Solution

1. Step 1: Recall resource route conventions for destroy

   The destroy method is called with HTTP DELETE on the resource URI with the ID, e.g., DELETE /photos/{id}.

2. Step 2: Match options to this pattern

   DELETE /photos/5 matches DELETE /photos/5. Other options use wrong HTTP methods or incorrect URLs.

3. Final Answer:

   DELETE /photos/5 -> Option D

4. Quick Check:

   Destroy = DELETE /resource/{id} [OK]

Hint: Destroy uses DELETE method on /resource/{id} URL [OK]

Common Mistakes:

• Using GET or POST instead of DELETE for destroy
• Adding extra path segments like /destroy or /delete
• Confusing PUT with DELETE method

4. Consider this route registration:
Route::resource('users', UserController::class);
Which of the following code snippets will cause a runtime error when trying to access the show method?

medium

A. public function show() { return 'User not found'; }

B. public function show(User $user) { return $user; }

C. public function show($id) { return view('user.show', compact('id')); }

D. public function show($id) { return User::findOrFail($id); }

Solution

1. Step 1: Understand show method parameter requirements

   The show method expects either an ID parameter or a model instance via route model binding.

2. Step 2: Analyze each option

   public function show() { return 'User not found'; } has no parameter, so Laravel cannot pass the required ID or model, causing a runtime error. Others have correct parameters.

3. Final Answer:

   public function show() { return 'User not found'; } -> Option A

4. Quick Check:

   Show method must accept ID or model parameter [OK]

Hint: Show method needs parameter for ID or model [OK]

Common Mistakes:

• Omitting parameters in show method
• Using wrong parameter types without binding
• Ignoring route model binding requirements

5. You want to create a resource controller for Product but only want to generate routes for index, show, and store methods. Which is the correct way to register this in routes/web.php?

hard

A. Route::resource('products', ProductController::class)->except(['create', 'edit']);

B. Route::resource('products', ProductController::class)->only(['index', 'show', 'store']);

C. Route::resource('products', ProductController::class)->skip(['create', 'edit']);

D. Route::resource('products', ProductController::class)->filter(['index', 'show', 'store']);

Solution

1. Step 1: Recall how to limit resource routes

   Laravel allows limiting routes using the only method with an array of method names.

2. Step 2: Evaluate each option

   A uses except(['create', 'edit']) which excludes only create and edit, leaving index, store, show, update, and destroy. B correctly uses only(['index', 'show', 'store']). C and D use invalid methods skip and filter.

3. Final Answer:

   Route::resource('products', ProductController::class)->only(['index', 'show', 'store']); -> Option B

4. Quick Check:

   Limit resource routes with only([...]) [OK]

Hint: Use ->only([...]) to limit resource controller routes [OK]

Common Mistakes:

• Using invalid methods like skip or filter
• Confusing only with except
• Not passing array to only method