What is the usage of laravel contract
In laravel, contracts refer to a series of interfaces that define core services provided by the framework to facilitate the development of third-party interface developers. The implementation of all contracts constitutes all core tasks of the framework, and can Understand the role of a given function through contracts.
#The operating environment of this article: Windows 10 system, Laravel version 6, Dell G3 computer.
What is the usage of laravel contract
What is the contract
The contract in Laravel refers to a series of interfaces provided by the framework that define core services, such as cache, queue, log The interface, the contract is the interface
Why do we need to define the interface
The purpose of defining the interface is decoupling
When we depend on the cache instance, laravel implements it as follows:
For example: We choose to use memcached cache driver
use Illuminate\Contracts\Cache\Repository as Cache; class Repository{ /** * 创建一个新的Repository实例 * * @param Cache $cache * @return void */ public function __construct(Cache $cache) { $this->cache = $cache; } }
Do not define the interface
If we do not define the interface we must write like this
use Memcached; class Repository{ /** * 创建一个新的Repository实例 * * @param Cache $cache * @return void */ public function __construct(Memcached $cache) { $this->cache = $cache; } }
This way when we need to switch the cache driver to redis When , we must go to the controller and change the type convention of dependency injection to redis, because the implementation of redis is not necessarily exactly the same as Memcached, which means that the Memcached cache is tightly coupled with laravel
What is Loose coupling
What is loose coupling? When the system is upgraded and an implementation needs to be modified (such as upgrading from Memcached to Redis), the code base can not be modified, and only the configuration needs to be modified. It is considered loosely coupled when the upgrade can be completed!
One contract has two, or multiple implementations
Personally, since the contract is finalized, the corresponding implementation should be two, or more implementations, or there will be in the near future There are two or more implementations, and the contract is here to stipulate so many implementations. If there is only one implementation, it feels like the contract is useless!
Summary
The definition contract is an agreement for the implementation of a set of functions to facilitate the development of third-party interface developers
The contract is more like a A directory index of the framework. The implementation of all contracts constitutes all the core services of the framework, and you can quickly understand what this set of functions does through the contract.
For cache classes, the cache contract is to stipulate Various cache implementations (Memcached, Redis, file cache) need to implement functions
[Related recommendations: laravel video tutorial]
The above is the detailed content of What is the usage of laravel contract. 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



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.

Compare the data processing capabilities of Laravel and CodeIgniter: ORM: Laravel uses EloquentORM, which provides class-object relational mapping, while CodeIgniter uses ActiveRecord to represent the database model as a subclass of PHP classes. Query builder: Laravel has a flexible chained query API, while CodeIgniter’s query builder is simpler and array-based. Data validation: Laravel provides a Validator class that supports custom validation rules, while CodeIgniter has less built-in validation functions and requires manual coding of custom rules. Practical case: User registration example shows Lar

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.

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 ?

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.

Comparing Laravel's Blade and CodeIgniter's Twig template engine, choose based on project needs and personal preferences: Blade is based on MVC syntax, which encourages good code organization and template inheritance. Twig is a third-party library that provides flexible syntax, powerful filters, extended support, and security sandboxing.

Laravel - Artisan Console - Laravel framework provides three primary tools for interaction through command-line namely: Artisan, Ticker and REPL. This chapter explains about Artisan in detail.
