This Symfony bundle augments geekcell/php-ddd with framework-specific implementations to enable seamless domain driven design in a familiar environment.

To use this bundle, require it in Composer

composer require geekcell/ddd-bundle

• Aggregate Root
• Repositories
• Command & Query Bus
• Supporting Tools

Extend from AggregateRoot to record and commit domain events. Domain events must implement the (marker) interface DomainEvent. Events will be dispatched via the currently configured Symfony event dispatcher.

use GeekCell\Ddd\Contracts\Domain\Event as DomainEvent; use GeekCell\DddBundle\Domain\AggregateRoot; class OrderPlacedEvent implements DomainEvent { public function __construct( private readonly Order $order, ) { } // Getters etc. } class Order extends AggregateRoot { public function save(): void { $this->record(new OrderPlacedEvent($this)); } // ... } $order = new Order( /* ... */ ); $order->save(); $order->commit(); // All recorded events will be dispatched and released

Hint: If you want to dispatch an event directly, use AggregateRoot::dispatch() instead of AggregateRoot::record().

If you cannot (or don't want to) extend from AggregateRoot, you can alternative use DispatchableTrait to add dispatching capabilities to any class. The former is however the recommended way.

coming soon...

You can use CommandBus and QueryBus as services to implement CQRS. Internally, both buses will use the Symfony messenger as "backend".

// src/Application/Query/TopRatedBookQuery.php use GeekCell\Ddd\Contracts\Application\Query; class TopRatedBooksQuery implements Query { public function __construct( private readonly string $category, private readonly int $sinceDays, private readonly int $limit = 10, ) { } // Getters etc. } // src/Application/Query/TopRatedBookQueryHandler.php use GeekCell\Ddd\Contracts\Application\QueryHandler; #[AsMessageHandler] class TopRatedBookQueryHandler implements QueryHandler { public function __construct( private readonly BookRepository $repository, ) { } public function __invoke(TopRatedBookQuery $query) { $books = $this->repository ->findTopRated($query->getCategory(), $query->getSinceDays()) ->paginate($query->getLimit()); return $books; } } // src/Infrastructure/Http/Controller/BookController.php use GeekCell\Ddd\Contracts\Application\QueryBus; class BookController extends AbstractController { public function __construct( private readonly QueryBus $queryBus, ) { } #[Route('/books/top-rated')] public function getTopRated(Request $request) { $query = new TopRatedBooksQuery( /* extract from request */ ); $topRatedBooks = $this->queryBus->dispatch($query); // ... } }

Facades are heavily inspired by Laravel's Facades and are more or less singletons on steroids. They are basically a shortcut to services inside the DIC.

use GeekCell\DddBundle\Support\Facades\EventDispatcher; EventDispatcher::dispatch($someEvent); // same as: $container->get('event_dispatcher')->dispatch($someEvent);

You can create your own facades by extending from Facade and implementing the Facade::getFacadeAccessor() method to return the DIC service alias.

use GeekCell\DddBundle\Support\Facades\Facade; class Logger extends Facade { protected static function getFacadeAccessor(): string { return 'logger'; } }

Although facades are better testable than regular singletons, it is highly recommended to only use them sparringly and always prefer normal dependency injection when possible.

This bundle adds several maker bundle commands to generate commonly used components.

This command can be used to generate:

• The domain model class.
• A repository class for the model.
• The model's identity class as value object (optional).
• A Doctrine database entity configuration, either as annotation or separate config file (optional).
• A custom Doctrine type for the model's identity class (optional).

Description: Creates a new domain model class Usage: make:ddd:model [options] [--] [<name>] Arguments: name The name of the model class (e.g. Customer) Options: --aggregate-root Marks the model as aggregate root --entity=ENTITY Use this model as Doctrine entity --with-identity=WITH-IDENTITY Whether an identity value object should be created --with-suffix Adds the suffix "Model" to the model class name

These commands can be used to generate:

• A query and query handler class.
• A command and command handler class.

The query / command generated is just an empty class. The handler class is registered as a message handler for the configured Symfony Messenger.

Description: Creates a new query|command class and handler Usage: make:ddd:query|command [<name>] Arguments: name The name of the query|command class (e.g. Customer)

This command can be used to generate a controller with optional QueryBus and CommandBus dependencies.

Description: Creates a new controller class Usage: make:ddd:controller [options] [--] [<name>] Arguments: name The name of the model class (e.g. Customer) Options: --include-query-bus Add a query bus dependency --include-command-bus Add a command bus dependency

This command can be used to generate an Api Platform resource. Minimum required version is 2.7 for the PHP attributes support.

Description: Creates a new API Platform resource Usage: make:ddd:resource [options] [--] [<name>] Arguments: name The name of the model class to create the resource for (e.g. Customer). Model must exist already. Options: --config Config flavor to create (attribute|xml).