Laravel-DDD is a toolkit to support domain driven design (DDD) patterns in Laravel applications. One of the pain points when adopting DDD is the inability to use Laravel's native make:model
artisan command to properly generate domain models, since domain models are not intended to be stored in the App/Models/*
namespace. This package aims to fill the gaps by providing an equivalent command, ddd:model
, plus many more.
You can install the package via composer:
composer require lunarstorm/laravel-ddd
You may then initialize the package using the ddd:install
artisan command. This command will publish the config file, register the domain path in your project's composer.json psr-4 autoload configuration on your behalf, and allow you to publish generator stubs for customization if needed.
php artisan ddd:install
Laravel | LaravelDDD |
---|---|
9.x - 10.24.x | 0.x |
10.25.x | 1.x |
11.x | 1.x |
For 0.x usage, please refer to the 0.x README.
Things to be aware of when upgrading from 0.x:
- If the config file was published, it should be removed, re-published, and re-configured according to the latest format. A helper command
ddd:upgrade
is available to assist with this. - If stubs were published, they should also be re-published and inspected to ensure everything is up-to-date.
- In production,
ddd:cache
should be run during the deployment process to optimize autoloading. See the Autoloading in Production section for more details.
All domain generator commands use the following syntax:
# Specifying the domain as an option
php artisan ddd:{object} {name} --domain={domain}
# Specifying the domain as part of the name (short-hand syntax)
php artisan ddd:{object} {domain}:{name}
# Not specifying the domain at all, which will then prompt
# prompt for it (with auto-completion)
php artisan ddd:{object} {name}
The following generators are currently available, shown using short-hand syntax:
# Generate a domain model
php artisan ddd:model Invoicing:Invoice
# Generate a domain model with factory
php artisan ddd:model Invoicing:Invoice -f
php artisan ddd:model Invoicing:Invoice --factory
# Generate a domain factory
php artisan ddd:factory Invoicing:InvoiceFactory
php artisan ddd:factory Invoicing:InvoiceFactory --model=Invoice # optionally specifying the model
# Generate a data transfer object
php artisan ddd:dto Invoicing:LineItemPayload
# Generates a value object
php artisan ddd:value Shared:DollarAmount
# Generates a view model
php artisan ddd:view-model Invoicing:ShowInvoiceViewModel
# Generates an action
php artisan ddd:action Invoicing:SendInvoiceToCustomer
# Extended Commands
# These extend Laravel's respective make:* commands and places the objects into the domain layer
php artisan ddd:cast Invoicing:MoneyCast
php artisan ddd:channel Invoicing:InvoiceChannel
php artisan ddd:command Invoicing:InvoiceDeliver
php artisan ddd:enum Customer:CustomerType # Laravel 11+ only
php artisan ddd:event Invoicing:PaymentWasReceived
php artisan ddd:exception Invoicing:InvoiceNotFoundException
php artisan ddd:job Invoicing:GenerateInvoicePdf
php artisan ddd:listener Invoicing:HandlePaymentReceived
php artisan ddd:mail Invoicing:OverduePaymentReminderEmail
php artisan ddd:notification Invoicing:YourPaymentWasReceived
php artisan ddd:observer Invoicing:InvoiceObserver
php artisan ddd:policy Invoicing:InvoicePolicy
php artisan ddd:provider Invoicing:InvoiceServiceProvider
php artisan ddd:resource Invoicing:InvoiceResource
php artisan ddd:rule Invoicing:ValidPaymentMethod
php artisan ddd:scope Invoicing:ArchivedInvoicesScope
Generated objects will be placed in the appropriate domain namespace as specified by ddd.namespaces.*
in the configuration file.
# Show a summary of current domains in the domain folder
php artisan ddd:list
# Cache domain manifests (used for autoloading)
php artisan ddd:cache
# Clear the domain cache
php artisan ddd:clear
Subdomains can be specified with dot notation wherever a domain option is accepted.
# Domain/Reporting/Internal/ViewModels/MonthlyInvoicesReportViewModel
php artisan ddd:view-model Reporting.Internal:MonthlyInvoicesReportViewModel
# Domain/Reporting/Customer/ViewModels/MonthlyInvoicesReportViewModel
php artisan ddd:view-model Reporting.Customer:MonthlyInvoicesReportViewModel
# (supported by all commands where a domain option is accepted)
This package ships with opinionated (but sensible) configuration defaults. You may customize by publishing the config file and generator stubs as needed:
php artisan vendor:publish --tag="ddd-config"
php artisan vendor:publish --tag="ddd-stubs"
Note that the extended commands do not publish ddd-specific stubs, and inherit the respective application-level stubs published by Laravel.
Autoloading behaviour can be configured with the ddd.autoload
configuration option. By default, domain providers, commands, policies, and factories are auto-discovered and registered.
'autoload' => [
'providers' => true,
'commands' => true,
'policies' => true,
'factories' => true,
],
When ddd.autoload.providers
is enabled, any class within the domain layer extending Illuminate\Support\ServiceProvider
will be auto-registered as a service provider.
When ddd.autoload.commands
is enabled, any class within the domain layer extending Illuminate\Console\Command
will be auto-registered as a command when running in console.
When ddd.autoload.policies
is enabled, the package will register a custom policy discovery callback to resolve policy names for domain models, and fallback to Laravel's default for all other cases. If your application implements its own policy discovery using Gate::guessPolicyNamesUsing()
, you should set ddd.autoload.policies
to false
to ensure it is not overridden.
When ddd.autoload.factories
is enabled, the package will register a custom factory discovery callback to resolve factory names for domain models, and fallback to Laravel's default for all other cases. Note that this does not affect domain models using the Lunarstorm\LaravelDDD\Factories\HasDomainFactory
trait. Where this is useful is with regular models in the domain layer that use the standard Illuminate\Database\Eloquent\Factories\HasFactory
trait.
If your application implements its own factory discovery using Factory::guessFactoryNamesUsing()
, you should set ddd.autoload.factories
to false
to ensure it is not overridden.
You may disable autoloading by setting the respective autoload options to false
in the configuration file as needed, or by commenting out the autoload configuration entirely.
// 'autoload' => [
// 'providers' => true,
// 'commands' => true,
// 'policies' => true,
// 'factories' => true,
// ],
In production, you should cache the autoload manifests using the ddd:cache
command as part of your application's deployment process. This will speed up the auto-discovery and registration of domain providers and commands. The ddd:clear
command may be used to clear the cache if needed.
This is the content of the published config file (ddd.php
):
return [
/*
|--------------------------------------------------------------------------
| Domain Path
|--------------------------------------------------------------------------
|
| The path to the domain folder relative to the application root.
|
*/
'domain_path' => 'src/Domain',
/*
|--------------------------------------------------------------------------
| Domain Namespace
|--------------------------------------------------------------------------
|
| The root domain namespace.
|
*/
'domain_namespace' => 'Domain',
/*
|--------------------------------------------------------------------------
| Domain Object Namespaces
|--------------------------------------------------------------------------
|
| This value contains the default namespaces of generated domain
| objects relative to the domain namespace of which the object
| belongs to.
|
| e.g., Domain\Invoicing\Models\*
| Domain\Invoicing\Data\*
| Domain\Invoicing\ViewModels\*
| Domain\Invoicing\ValueObjects\*
| Domain\Invoicing\Actions\*
|
*/
'namespaces' => [
'model' => 'Models',
'data_transfer_object' => 'Data',
'view_model' => 'ViewModels',
'value_object' => 'ValueObjects',
'action' => 'Actions',
'cast' => 'Casts',
'channel' => 'Channels',
'command' => 'Commands',
'enum' => 'Enums',
'event' => 'Events',
'exception' => 'Exceptions',
'factory' => 'Database\Factories',
'job' => 'Jobs',
'listener' => 'Listeners',
'mail' => 'Mail',
'notification' => 'Notifications',
'observer' => 'Observers',
'policy' => 'Policies',
'provider' => 'Providers',
'resource' => 'Resources',
'rule' => 'Rules',
'scope' => 'Scopes',
],
/*
|--------------------------------------------------------------------------
| Base Model
|--------------------------------------------------------------------------
|
| The base class which generated domain models should extend. By default,
| generated domain models will extend `Domain\Shared\Models\BaseModel`,
| which will be created if it doesn't already exist.
|
*/
'base_model' => 'Domain\Shared\Models\BaseModel',
/*
|--------------------------------------------------------------------------
| Base DTO
|--------------------------------------------------------------------------
|
| The base class which generated data transfer objects should extend. By
| default, generated DTOs will extend `Spatie\LaravelData\Data` from
| Spatie's Laravel-data package, a highly recommended data object
| package to work with.
|
*/
'base_dto' => 'Spatie\LaravelData\Data',
/*
|--------------------------------------------------------------------------
| Base ViewModel
|--------------------------------------------------------------------------
|
| The base class which generated view models should extend. By default,
| generated domain models will extend `Domain\Shared\ViewModels\BaseViewModel`,
| which will be created if it doesn't already exist.
|
*/
'base_view_model' => 'Domain\Shared\ViewModels\ViewModel',
/*
|--------------------------------------------------------------------------
| Base Action
|--------------------------------------------------------------------------
|
| The base class which generated action objects should extend. By default,
| generated actions are based on the `lorisleiva/laravel-actions` package
| and do not extend anything.
|
*/
'base_action' => null,
/*
|--------------------------------------------------------------------------
| Autoloading
|--------------------------------------------------------------------------
|
| Configure whether domain providers, commands, policies, and factories
| should be auto-discovered and registered.
|
*/
'autoload' => [
/**
* When enabled, any class within the domain layer extending `Illuminate\Support\ServiceProvider`
* will be auto-registered as a service provider
*/
'providers' => true,
/**
* When enabled, any class within the domain layer extending `Illuminate\Console\Command`
* will be auto-registered as a command when running in console.
*/
'commands' => true,
/**
* When enabled, the package will register a custom policy discovery callback to resolve policy names
* for domain models, and fallback to Laravel's default for all other cases.
*/
'policies' => true,
/**
* When enabled, the package will register a custom factory discovery callback to resolve factory names
* for domain models, and fallback to Laravel's default for all other cases.
*/
'factories' => true,
],
/*
|--------------------------------------------------------------------------
| Caching
|--------------------------------------------------------------------------
|
| The folder where the domain cache files will be stored. Used for domain
| autoloading.
|
*/
'cache_directory' => 'bootstrap/cache/ddd',
];
composer test
Please see CHANGELOG for more information on what has changed recently.
Please review our security policy on how to report security vulnerabilities.
The MIT License (MIT). Please see License File for more information.