What to write for laravel service

With the continuous development of Laravel, Service has become an important component of the Laravel framework. What is the role of Service? How to use Service in Laravel? In this article, we will introduce the relevant knowledge of Laravel Service in detail.

1. The role of Service

Service refers to the business logic used in the project, such as some business logic related to payment, employee management, data analysis, etc. In the Laravel framework, Service is mainly used to handle some tedious business logic and encapsulate it into a reusable component so that it can be called in multiple Controllers, Repositories, and Services, improving code reuse rate and reducing code redundancy.

Normally, Service and Repository are used to implement a series of business operations on data, but Service needs to be further encapsulated to achieve a high degree of abstraction and simplification of the business. Service accepts client requests, processes business logic, and returns results or throws exceptions.

Different from Repository, Service encapsulates a lot of business logic, and for different business functions, you can create multiple different Service classes to facilitate the logical division of code.

2. How to implement Service

When using Service, you should pay attention to two aspects: creating a Service class and calling the Service class where needed. The code will be explained in detail below.

1. Create Service

When creating a Service, you need to consider the function and caller of the Service. Under normal circumstances, some basic addition, deletion, modification and query operations are implemented in Service, as well as some other more specific business logic.

The following takes a user-registered Service as an example to show the conventional implementation of Service:

<?php

namespace AppServices;

use AppRepositoriesUserRepository;

class RegisterService
{
    protected $userRepository;

    /**
     * RegisterService constructor.
     *
     * @param UserRepository $userRepository
     */
    public function __construct(UserRepository $userRepository)
    {
        $this->userRepository = $userRepository;
    }

    /**
     * 用户注册.
     *
     * @param array $data
     *
     * @return mixed
     */
    public function register(array $data)
    {
        // TODO: 进一步验证
        $this->userRepository->create($data);
    }
}

In the above code, first namespace AppServices, and the class name of Service is RegisterService. The UserRepository object needs to be injected into the constructor. In Service, we implemented the user registration logic and used the create() method of UserRepository to create a new user in the database.

2. Call Service

After the Service is available, it needs to be called in Controller and Repository. The following takes calling RegisterService in Controller as an example to show the calling code:

<?php

namespace AppHttpControllers;

use AppHttpRequestsRegisterRequest;
use AppServicesRegisterService;

class RegisterController extends Controller
{
    public function register(RegisterRequest $request, RegisterService $registerService)
    {
        // TODO: 调用 Service 进行注册
        $registerService->register($request->validated());
    }
}

In the above code, when using RegisterService, you need to pass in the UserRepository object in its constructor, and when calling, you need to pass in the method of RegisterController Inject the RegisterService object into the parameter.

3. Other issues that need attention in Service

You also need to pay attention to the following issues when using Service in Laravel:

1. Service is just a class and can depend on Other Services, Repositories, or other Classes still need to inject dependencies in the constructor when using them.
2. Service needs to implement specific business logic, which also requires that Service needs to be kept simple and lightweight. If the business implemented by the Service is too complex, you need to consider splitting the Service. It is generally recommended that each Service only implements a single function.
3. Do not include view-level logic processing in Service. The logic in Service should have nothing to do with the logic of the controller and other called services.

4. Conclusion

Service is one of the important components of Laravel, and its advantages as a business logic component are very obvious. After Laravel 5.8/6, Laravel officially introduced a more convenient Service automatic registration mechanism, making it easier to integrate Service. For increasingly complex business logic, Service organization code is clearer and easier to understand, simplifies code complexity, and has better scalability and maintainability.

The above is the detailed content of What to write for laravel service. For more information, please follow other related articles on the PHP Chinese website!