Resource routes in Laravel - Performance & Optimization

Performance: Resource routes

MEDIUM IMPACT

Resource routes affect the routing system's efficiency and the initial request handling speed in Laravel applications.

Defining routes for CRUD operations in a Laravel app

Laravel

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

Defines all CRUD routes in one line, reducing routing table size and improving route matching efficiency.

📈 Performance GainSingle route definition reduces routing table size and speeds up route matching.

Defining routes for CRUD operations in a Laravel app

Laravel

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

Manually defining each route increases routing table size and can slow down route matching and maintenance.

📉 Performance CostAdds multiple route entries increasing route matching time linearly with number of routes.

Performance Comparison

Pattern	Routing Table Size	Route Matching Time	Maintenance Cost	Verdict
Manual route definitions for each CRUD action	Large (7 entries per resource)	Higher due to more entries	High, repetitive code	[X] Bad
Single resource route definition	Small (1 entry per resource)	Lower due to fewer entries	Low, concise code	[OK] Good

Rendering Pipeline

Resource routes simplify the routing table, which reduces the time Laravel takes to match incoming requests to controllers before rendering the response.

→Routing

→Controller Dispatch

→Response Generation

⚠️ BottleneckRouting stage due to large number of route definitions

Core Web Vital Affected

LCP

Resource routes affect the routing system's efficiency and the initial request handling speed in Laravel applications.

Optimization Tips

1Use Route::resource to define CRUD routes in one line.

2Fewer route entries mean faster route matching and better LCP.

3Avoid manual repetitive route definitions to reduce routing table size.

Performance Quiz - 3 Questions

How does using resource routes in Laravel affect route matching performance?

A It reduces the number of route entries, speeding up route matching.

B It increases the number of route entries, slowing down route matching.

C It has no effect on route matching performance.

D It disables route caching, reducing performance.

DevTools: Laravel Telescope or Debugbar

How to check: Open Telescope or Debugbar during a request and check the routing section for number of routes matched and time taken.

What to look for: Lower route matching time and fewer route entries indicate better performance.

Practice

1. What does the Route::resource('photos', PhotoController::class) method do in Laravel?

easy

A. Creates multiple routes for common CRUD actions automatically.

B. Creates a single route for the index method only.

C. Creates routes only for the create and edit methods.

D. Deletes all existing routes related to photos.

Solution

1. Step 1: Understand the purpose of Route::resource

   This method generates routes for all standard CRUD actions (index, create, store, show, edit, update, destroy) automatically.

2. Step 2: Recognize the effect on routes

   It saves time by creating multiple routes with correct HTTP verbs and URLs for the resource controller.

3. Final Answer:

   Creates multiple routes for common CRUD actions automatically. -> Option A

4. Quick Check:

   Resource routes = multiple CRUD routes [OK]

Hint: Resource routes generate all CRUD URLs in one line [OK]

Common Mistakes:

• Thinking it creates only one route
• Confusing resource with single route methods
• Assuming it deletes routes

2. Which of the following is the correct syntax to create resource routes for a controller named PostController?

easy

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

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

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

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

Solution

1. Step 1: Identify correct controller reference syntax

   In Laravel, the controller class should be passed using the ::class constant without quotes.

2. Step 2: Check each option

   Route::resource('posts', PostController::class); correctly uses PostController::class without quotes, which is the modern and recommended syntax.

3. Final Answer:

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

4. Quick Check:

   Use ControllerName::class without quotes [OK]

Hint: Use ControllerName::class without quotes for resource routes [OK]

Common Mistakes:

• Passing controller name as a string with quotes
• Omitting ::class
• Using quotes around ::class

3. Given the route definition Route::resource('books', BookController::class)->only(['index', 'show']);, which URLs will be available?

medium

A. /books/create (GET) and /books/{book}/edit (GET)

B. /books (GET) and /books/{book} (GET)

C. /books (POST) and /books/{book} (DELETE)

D. /books/{book} (PUT) and /books/{book} (PATCH)

Solution

1. Step 1: Understand the only() method

   The only() method limits resource routes to specified actions. Here, only 'index' and 'show' routes are created.

2. Step 2: Identify routes for index and show

   Index route is GET /books, show route is GET /books/{book}.

3. Final Answer:

   /books (GET) and /books/{book} (GET) -> Option B

4. Quick Check:

   only(['index','show']) = GET /books and GET /books/{id} [OK]

Hint: only(['index','show']) creates just list and detail GET routes [OK]

Common Mistakes:

• Confusing HTTP verbs for actions
• Assuming create/edit routes are included
• Mixing POST or DELETE with index/show

4. What is wrong with this route definition?

Route::resource('users', UserController::class)->except('store');

medium

A. The except() method requires an array, not a string.

B. UserController::class should be a string.

C. Resource routes cannot use except() method.

D. The route name 'users' is invalid.

Solution

1. Step 1: Check except() method usage

   The except() method expects an array of action names to exclude, not a single string.

2. Step 2: Identify correct syntax

   It should be except(['store']) with square brackets to pass an array.

3. Final Answer:

   The except() method requires an array, not a string. -> Option A

4. Quick Check:

   Use except(['action']) with array brackets [OK]

Hint: Pass array to except(), not a single string [OK]

Common Mistakes:

• Passing string instead of array to except()
• Using quotes incorrectly around controller class
• Thinking except() is not allowed

5. You want to create resource routes for ArticleController but only allow routes for creating, storing, and editing articles. Which is the correct route definition?

hard

A. Route::resource('articles', ArticleController::class)->only(['create', 'store', 'edit']);

B. Route::resource('articles', ArticleController::class)->only(['create', 'edit']);

C. Route::resource('articles', ArticleController::class)->except(['index', 'show', 'update', 'destroy']);

D. Route::resource('articles', ArticleController::class)->except(['store']);

Solution

1. Step 1: Identify required actions

   We want routes for create, store, and edit only.

2. Step 2: Use except() to exclude unwanted actions

   Excluding index, show, update, and destroy leaves only create, store, and edit routes.

3. Step 3: Confirm only() option

   Route::resource('articles', ArticleController::class)->only(['create', 'store', 'edit']); correctly includes the store route, but using except() as in Route::resource('articles', ArticleController::class)->except(['index', 'show', 'update', 'destroy']); is also correct and often preferred for excluding unwanted routes.

4. Final Answer:

   Route::resource('articles', ArticleController::class)->except(['index', 'show', 'update', 'destroy']); -> Option C

5. Quick Check:

   except(['index','show','update','destroy']) = create, store, edit routes [OK]

Hint: Use except() to exclude unwanted routes for precise control [OK]

Common Mistakes:

• Using only() but missing store route
• Excluding wrong actions
• Confusing create and store routes