Every time you access an URL on a Laravel application, many things happen under the hood to process the given request.
If you take a quick look at the
kernel.php file, you’ll see some of the “tasks” that are going to be processed for each request.
This is just the “middleware” layer, and depending on the complexity of your application, you may have a lot of database queries, third-party API calls and so on.
Read more about the Laravel Lifecycle here: Request Lifecycle - Laravel - The PHP Framework For Web Artisans
Sometimes, there is no easy way to go around and “recycle” part of the processed data for further requests, but in Laravel, you can use “Cache” to store some data temporarily.
So, for instance, in your controller you can have something like:
The next time you request the same
Post::class Laravel will return the data from the cache storage instead of hitting the database again.
This is just fine in most cases, but you can go even further.
Caching an entire response
spatie/laravel-responsecache is a package developed by the spatie.be team that allows you to store an entire response-object in cache, so, if a given URL was already crawled, the next user will get a faster response because the application won’t have to run through the entire lifecycle all over again.
To install this package in your Laravel application just run the following command from your terminal:
composer require spatie/laravel-responsecache
And register the middlewares in your
To learn more about this package, you can read the official documentation here: GitHub - spatie/laravel-responsecache: Speed up a Laravel app by caching the entire response
My current Implementation
At the moment of this writing, I’m using this package on my website using the base setup described above, and registering all the routes that I want to cache under the same group as follows:
What about content updates?
By default, the package will store a response for a week, so that would be a problem if you update the content for a cached URL and you don’t handle that properly.
I solved this problem by creating a new
PostObserver to listen for the
updated() methods to remove the specific article from cache every time one of those events are fired.
Remember you’ll need to register the observers in your
So, now every time an article is updated, the observer will take care of removing that URL from the cache.
Using cache in the responses is a great approach to speed up your application, although you may want to be careful with it, primarily when you use real-time data or some user-specific information.