Practical application examples of Redis in Laravel projects
This article mainly introduces you to the relevant information about the application of Redis in the Laravel project. The article introduces it in great detail through sample code. It has certain reference learning value for everyone to learn or use Laravel. Friends who need it can follow below. Let’s learn together.
Preface
This article mainly introduces to you the application examples of Redis in Laravel project, and shares them for your reference and study. The following words Without further ado, let’s take a look at the detailed introduction:
After a preliminary understanding of the application of Redis in Laravel, let’s imagine such an application scenario. If the statistics of the number of views of an article or post only increase each time One page view
will add a new data to the database. If the request is too large, it will consume the database. Then can we have other solutions
The solution here is that even if your website has a large number of requests, make changes in the cache every time a visit is added. As for refreshing the Mysql database, you can customize it to
how many minutes to refresh or access. When the amount reaches a certain amount, refresh the database so that the data is accurate and the efficiency is much higher than directly refreshing the database each time.
Now that the corresponding solution is given, we will start to implement it
Let's take the browsing of a post as an example. We first create the corresponding controller
$ php artisan make:controller PostController
and then generate the Model
we need to use.
$ php artisan make:model Post -m
Fill in the field content of the migration table of posts
Schema::create('posts', function (Blueprint $table) { $table->increments('id'); $table->string("title"); $table->string("content"); $table->integer('view_count')->unsigned(); $table->timestamps(); });
There is also the Seeder filling data of our test data
$factory->define(App\Post::class, function (Faker\Generator $faker) { return [ 'title' => $faker->sentence, 'content' => $faker->paragraph, 'view_count' => 0 ]; });
Define the access route of the post
Route::get('/post/{id}', 'PostController@showPost');
Of course we still need to write our access, that is, the browsing event (in app/providers/EventServiceProvider Definition)
protected $listen = [ 'App\Events\PostViewEvent' => [ // 'App\Listeners\EventListener', 'App\Listeners\PostEventListener', ], ];
Execution event generation monitoring
$ php artisan event:generate
The relevant routing methods were defined before and now let’s implement them:
public function showPost(Request $request,$id) { //Redis缓存中没有该post,则从数据库中取值,并存入Redis中,该键值key='post:cache'.$id生命时间5分钟 $post = Cache::remember('post:cache:'.$id, $this->cacheExpires, function () use ($id) { return Post::whereId($id)->first(); }); //获取客户端请求的IP $ip = $request->ip(); //触发浏览次数统计时间 event(new PostViewEvent($post, $ip)); return view('posts.show', compact('post')); }
It can be seen here that using Redis as the cache driver will also obtain the obtained IP. The purpose is to prevent the same IP from being refreshed multiple times to increase the number of views
Similarly, each browsing will trigger the event we defined before and pass it into our post and id parameters
The naming of the Redis key is divided by: This can be understood as a hierarchical directory. It can be seen clearly in the visualization tool
The next step is to give the view file of our posts.show
<html lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Bootstrap Template</title> <!-- 新 Bootstrap 核心 CSS 文件 --> <link rel="stylesheet" href="//cdn.bootcss.com/bootstrap/3.3.5/css/bootstrap.min.css" rel="external nofollow" > <style> html,body{ width: 100%; height: 100%; } *{ margin: 0; border: 0; } .jumbotron{ margin-top: 10%; } .jumbotron>span{ margin: 10px; } </style> </head> <body> <p class="container"> <p class="row"> <p class="col-xs-12 col-md-12"> <p class="jumbotron"> <h1>Title:{{$post->title}}</h1> <span class="glyphicon glyphicon-eye-open" aria-hidden="true"> {{$post->view_count}} views</span> <p>Content:{{$post->content}}</p> </p> </p> </p> </p> <!-- jQuery文件--> <script src="//cdn.bootcss.com/jquery/1.11.3/jquery.min.js"></script> <!-- 最新的 Bootstrap 核心 JavaScript 文件 --> <script src="//cdn.bootcss.com/bootstrap/3.3.5/js/bootstrap.min.js"></script> <script> </script> </body> </html>
To initialize our event is to receive these parameters
class PostViewEvent { use Dispatchable, InteractsWithSockets, SerializesModels; public $ip; public $post; /** * PostViewEvent constructor. * @param Post $post * @param $ip */ public function __construct(Post $post, $ip) { $this->post = $post; $this->ip = $ip; } /** * Get the channels the event should broadcast on. * * @return Channel|array */ public function broadcastOn() { return new PrivateChannel('channel-name'); } }
The most important thing is to write our monitoring event:
class PostEventListener { /** * 一个帖子的最大访问数 */ const postViewLimit = 20; /** * 同一用户浏览同一个帖子的过期时间 */ const ipExpireSec = 200; /** * Create the event listener. * */ public function __construct() { } /** * @param PostViewEvent $event */ public function handle(PostViewEvent $event) { $post = $event->post; $ip = $event->ip; $id = $post->id; //首先判断下ipExpireSec = 200秒时间内,同一IP访问多次,仅仅作为1次访问量 if($this->ipViewLimit($id, $ip)){ //一个IP在300秒时间内访问第一次时,刷新下该篇post的浏览量 $this->updateCacheViewCount($id, $ip); } } /** * 限制同一IP一段时间内得访问,防止增加无效浏览次数 * @param $id * @param $ip * @return bool */ public function ipViewLimit($id, $ip) { $ipPostViewKey = 'post:ip:limit:'.$id; //Redis命令SISMEMBER检查集合类型Set中有没有该键,Set集合类型中值都是唯一 $existsInRedisSet = Redis::command('SISMEMBER', [$ipPostViewKey, $ip]); //如果集合中不存在这个建 那么新建一个并设置过期时间 if(!$existsInRedisSet){ //SADD,集合类型指令,向ipPostViewKey键中加一个值ip Redis::command('SADD', [$ipPostViewKey, $ip]); //并给该键设置生命时间,这里设置300秒,300秒后同一IP访问就当做是新的浏览量了 Redis::command('EXPIRE', [$ipPostViewKey, self::ipExpireSec]); return true; } return false; } /** * 达到要求更新数据库的浏览量 * @param $id * @param $count */ public function updateModelViewCount($id, $count) { //访问量达到300,再进行一次SQL更新 $post = Post::find($id); $post->view_count += $count; $post->save(); } /** * 不同用户访问,更新缓存中浏览次数 * @param $id * @param $ip */ public function updateCacheViewCount($id, $ip) { $cacheKey = 'post:view:'.$id; //这里以Redis哈希类型存储键,就和数组类似,$cacheKey就类似数组名 如果这个key存在 if(Redis::command('HEXISTS', [$cacheKey, $ip])){ //哈希类型指令HINCRBY,就是给$cacheKey[$ip]加上一个值,这里一次访问就是1 $save_count = Redis::command('HINCRBY', [$cacheKey, $ip, 1]); //redis中这个存储浏览量的值达到30后,就去刷新一次数据库 if($save_count == self::postViewLimit){ $this->updateModelViewCount($id, $save_count); //本篇post,redis中浏览量刷进MySQL后,就把该篇post的浏览量清空,重新开始计数 Redis::command('HDEL', [$cacheKey, $ip]); Redis::command('DEL', ['laravel:post:cache:'.$id]); } }else{ //哈希类型指令HSET,和数组类似,就像$cacheKey[$ip] = 1; Redis::command('HSET', [$cacheKey, $ip, '1']); } } }
Finally, you can check the specific effect through our tool
The above is the detailed content of Practical application examples of Redis in Laravel projects. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Laravel - Artisan Commands - Laravel 5.7 comes with new way of treating and testing new commands. It includes a new feature of testing artisan commands and the demonstration is mentioned below ?

The latest versions of Laravel 9 and CodeIgniter 4 provide updated features and improvements. Laravel9 adopts MVC architecture and provides functions such as database migration, authentication and template engine. CodeIgniter4 uses HMVC architecture to provide routing, ORM and caching. In terms of performance, Laravel9's service provider-based design pattern and CodeIgniter4's lightweight framework give it excellent performance. In practical applications, Laravel9 is suitable for complex projects that require flexibility and powerful functions, while CodeIgniter4 is suitable for rapid development and small applications.

For beginners, CodeIgniter has a gentler learning curve and fewer features, but covers basic needs. Laravel offers a wider feature set but has a slightly steeper learning curve. In terms of performance, both Laravel and CodeIgniter perform well. Laravel has more extensive documentation and active community support, while CodeIgniter is simpler, lightweight, and has strong security features. In the practical case of building a blogging application, Laravel's EloquentORM simplifies data manipulation, while CodeIgniter requires more manual configuration.

When choosing a framework for large projects, Laravel and CodeIgniter each have their own advantages. Laravel is designed for enterprise-level applications, offering modular design, dependency injection, and a powerful feature set. CodeIgniter is a lightweight framework more suitable for small to medium-sized projects, emphasizing speed and ease of use. For large projects with complex requirements and a large number of users, Laravel's power and scalability are more suitable. For simple projects or situations with limited resources, CodeIgniter's lightweight and rapid development capabilities are more ideal.

For small projects, Laravel is suitable for larger projects that require strong functionality and security. CodeIgniter is suitable for very small projects that require lightweight and ease of use.

Laravel - Facades - Facades provide a static interface to classes that are available in the application's service container. Laravel facades serve as static proxies to underlying classes in the service container, providing the benefit of a terse, exp

Laravel - Dump Server - Laravel dump server comes with the version of Laravel 5.7. The previous versions do not include any dump server. Dump server will be a development dependency in laravel/laravel composer file.

Laravel - Pagination Customizations - Laravel includes a feature of pagination which helps a user or a developer to include a pagination feature. Laravel paginator is integrated with the query builder and Eloquent ORM. The paginate method automatical
