How and into which components is it recommended to transfer business logic from the controller when developing in Laravel?

In Laravel, it is recommended to move business logic from controllers to separate layers to keep controllers thin and responsible only for handling HTTP requests and forming responses. Main approaches:

• Services (Service Classes) — classes that encapsulate business logic, such as data processing, interaction with multiple models, etc.
• Repositories (Repository Pattern) — a layer for data operations, abstracting access to the database.
• Eloquent Models — can be used for business logic related to a specific entity, but it is better to avoid overloading models.
• Actions or Use Cases — separate classes that implement a specific action or scenario.

Example of a service:

class OrderService
{
    public function createOrder(array $data)
    {
        // Validation, order creation, discount logic, etc.
    }
}

// In the controller
public function store(Request $request, OrderService $orderService)
{
    $order = $orderService->createOrder($request->all());
    return response()->json($order);
}

This approach improves testability, reusability, and code maintenance.