What is the difference between contract and facade in laravel
Difference: 1. The contract refers to a series of interfaces provided by the framework that define core services, while the facade provides static interfaces for the classes of the IoC service container; 2. The contract can be regarded as the method definition interface of the framework function. , stores most methods, and the facade provides methods, provides static calls, and does not need to inject interfaces.
The operating environment of this tutorial: Windows 10 system, Laravel 6 version, DELL G3 computer.
What is the difference between contracts and facades in laravel
Introduction
Laravel’s Contracts are a set of interfaces that are provided by the framework and define core services . For example, the illuste\Contracts\Queue\Queue contract defines the methods required to queue a job, while the illuste\Contracts\Mail\Mailer contract defines the methods required to send mail. Contracts are also called contracts
In our previous study, we learned a lot of auxiliary functions and simple methods provided by the Facades facade, which can implement methods without type hints. In most cases, every Each facade has a corresponding contract method. Unlike facades, contracts allow you to display dependencies for class definitions.
When to use contracts
As discussed elsewhere As discussed, many of the decisions about using Contracts or Facades will come down to personal preference and the preferences of the development team. Both Contracts and Facades can be used to create powerful and well-tested Laravel applications. As long as you focus on the fact that a class should have a single responsibility, you'll find that the actual difference between using contracts or facades is actually very small.
How to use the contract
So, how to implement the contract? It's actually very simple.
Many classes in Laravel are resolved through the service container, including controllers, event listeners, middleware, queue tasks, and even routing closures. Therefore, to implement the contract, you simply "type-hint" the interface in the constructor of the resolved class.
For example, view this event listener:
<?php namespace App\Listeners; use App\Events\OrderWasPlaced; use App\Models\User; use Illuminate\Contracts\Redis\Factory; class CacheOrderInformation { /** * Redis 工厂实现 */ protected $redis; /** * 创建一个事件处理实例 * * @param Factory $redis * @return void */ public function __construct(Factory $redis) { $this->redis = $redis; } /** * 处理事件 * * @param OrderWasPlaced $event * @return void */ public function handle(OrderWasPlaced $event) { // } }
The difference between contract and facade
A contract actually refers to a series of definition cores provided by the framework The interface of the service, the keyword is this interface. Looking at the above code, you can understand what functions this interface provides. We can regard the contract as the method definition interface of the framework function. This interface stores the functions we need to use. Most methods.
The facade also provides methods, but every time we want to use the interface method, we need to inject the corresponding interface, which is very troublesome, so the facade was born to provide static calls. , no need to inject the interface.
[Related recommendations: laravel video tutorial]
The above is the detailed content of What is the difference between contract and facade in laravel. 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 - 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
