Route caching in Laravel - Step-by-Step Execution

Concept Flow - Route caching

Define routes in routes/web.php

↓

Run 'php artisan route:cache'

↓

Laravel compiles routes into cache file

↓

Cached routes used on requests

↓

Faster route resolution

↓

If routes change -> run 'php artisan route:cache' again

Routes are defined, then cached by a command, so Laravel loads them faster on each request.

Execution Sample

Laravel

Route::get('/home', function () {
    return 'Home page';
});

// Run in terminal:
// php artisan route:cache

Defines a route and caches all routes to speed up request handling.

Execution Table

Step	Action	Input/Command	Result	Notes
1	Define routes	Route::get('/home', ...)	Route registered in memory	Routes ready for caching
2	Run cache command	php artisan route:cache	Routes compiled and saved to cache file	Cache file created at bootstrap/cache/routes-v7.php
3	Handle request	GET /home	Route loaded from cache	No route parsing needed
4	Serve response	Return 'Home page'	Response sent quickly	Faster than uncached routes
5	Change routes	Add new route	Routes in memory updated	Cache is now outdated
6	Run cache command again	php artisan route:cache	Cache file updated	Cache refreshed with new routes

💡 Route cache speeds up route loading until routes change and cache is refreshed

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 5	After Step 6
routes_in_memory	empty	['/home' => closure]	['/home' => closure]	['/home' => closure, '/about' => closure]	['/home' => closure, '/about' => closure]
route_cache_file	none	none	exists with cached routes	exists with old cached routes	exists with updated cached routes

Key Moments - 2 Insights

Why do we need to run 'php artisan route:cache' again after changing routes?

Because the cached routes file does not update automatically. The execution_table rows 5 and 6 show that after changing routes, the cache is outdated until refreshed by running the command again.

What happens when a request comes in after routes are cached?

The request uses the cached routes file directly, skipping route parsing. See execution_table row 3 where the route is loaded from cache, making response faster.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'route_cache_file' after step 2?

A Cache file exists with cached routes

B Cache file does not exist

C Cache file is outdated

D Cache file is deleted

💡 Hint

Check variable_tracker row for 'route_cache_file' after Step 2

At which step does the route cache become outdated?

A Step 2

B Step 5

C Step 3

D Step 6

💡 Hint

Look at execution_table row 5 where routes change but cache is not refreshed

If you add a new route but do NOT run 'php artisan route:cache' again, what happens on request?

A New route works immediately

B Laravel throws an error

C Old cached routes are used, new route ignored

D Routes are automatically refreshed

💡 Hint

Refer to execution_table rows 5 and 6 about cache update necessity

Concept Snapshot

Route caching in Laravel:
- Define routes normally in routes files
- Run 'php artisan route:cache' to compile routes into a cache file
- Laravel loads routes from cache for faster request handling
- When routes change, rerun the cache command to refresh
- Speeds up route resolution by avoiding route parsing on each request

Full Transcript

Route caching in Laravel works by first defining your routes in the routes files. Then, you run the command 'php artisan route:cache' which compiles all routes into a single cache file. When a request comes in, Laravel loads routes from this cache file instead of parsing the routes again, making the response faster. If you change or add routes, you must run the cache command again to update the cache file. Otherwise, Laravel will keep using the old cached routes and ignore your changes. This process improves performance by reducing route loading time on every request.