laravel-actions

To move domain logic out of Laravel controllers, encapsulate business operations in invokable Action classes with strict typing and transactions. This creates a testable domain layer and aligns code structure with clear domain boundaries.

The invokable action pattern in Laravel uses classes with a single __invoke method to execute business operations. It enforces strict typing, dependency injection, and database transactions for reusable and composable workflows.

Structure complex Laravel workflows by injecting and invoking other action classes within a parent action. This composition approach allows you to build reusable operations for processes like user onboarding or order processing while maintaining testability.

Yes, you can unit test individual domain operations in Laravel actions because business logic is encapsulated in single invokable classes. This isolation makes testing specific domain steps easy without booting the entire application.

No, you do not need extra packages to use Laravel actions for domain logic. You can define a simple Action class with an __invoke method and call it from a controller or service using native dependency injection or the resolve() helper.

Use Laravel actions instead of standard controllers when your application needs clear domain boundaries, reusable workflows, and composable operations. Actions prevent fat controllers by moving complex business logic like order processing into a dedicated domain layer.