0008-laravel-actions

The best way to centralize Laravel domain logic is using invokable action classes with a single __invoke() entry point. This pattern encapsulates domain operations, keeping business rules out of controllers and listeners for consistent behavior.

Structure multi-step Laravel workflows by composing dependency-injected actions. One action can call other actions to coordinate side effects, validate domain rules, and orchestrate complex multi-step business processes from a single domain-centric location.

Ensure reliable Laravel database mutations by wrapping model changes inside DB::transaction() within your action. This transactional approach keeps state changes reliable, especially when coordinating multiple side effects like notifications and external service calls.

Yes, you can use dependency injection to compose Laravel actions. Injecting actions into other actions allows you to build complex domain workflows, enforce domain constraints, and coordinate side effects while maintaining a stateless, testable architecture.

You should avoid using invokable action classes for trivial CRUD operations that do not require complex domain rules or multi-step workflows. If a controller method handles simple, direct model interactions without scattered logic, an action class may add unnecessary boilerplate.