Does it support Doctrine transactions?

Yes, the provided configuration includes the doctrine_transaction middleware for the command bus to ensure atomicity during write operations.

Can I use this for non-API applications?

While the examples show API controllers, the CQRS pattern is applicable to any Symfony application where you want to separate domain logic from the presentation layer.

Does this skill require the Symfony Messenger component?

Yes, it is built specifically to leverage Symfony Messenger for dispatching messages through dedicated command and query buses.

What is the benefit of using separate buses for Commands and Queries?

Separate buses allow you to apply specific middleware to each; for example, you can enforce validation and transactions on commands while keeping queries fast and side-effect free.

Symfony CQRS & Messenger Handlers

Name: Symfony CQRS & Messenger Handlers
Author: MakFly

byMakFly

•

API Development

Implements Command Query Responsibility Segregation (CQRS) in Symfony applications using the Messenger component to decouple read and write logic.

About

This skill streamlines the implementation of the CQRS pattern within Symfony projects by providing a standardized structure for Commands, Queries, and their respective Handlers. By leveraging the Symfony Messenger component, it enables developers to separate side-effect-producing write operations from side-effect-free read operations through dedicated buses. This architecture improves maintainability, scalability, and testability, allowing for complex domain logic to be handled in isolation while optimizing read performance through dedicated models and SQL when necessary.

Key Features

Standardized project structure for Application, Domain, and Infrastructure layers
Integrated database transaction and validation middleware for Commands
Support for optimized Read Models using direct SQL or dedicated repositories
Pre-configured Messenger Handlers using the #[AsMessageHandler] attribute
21 GitHub stars
Separate Command and Query buses with specialized middleware configuration

Use Cases

Optimizing read-heavy performance by implementing dedicated read models alongside domain entities
Refactoring monolithic controllers into decoupled, testable command and query handlers
Building complex enterprise-grade Symfony applications that require a clean separation of concerns

About

Key Features

Standardized project structure for Application, Domain, and Infrastructure layers
Integrated database transaction and validation middleware for Commands
Support for optimized Read Models using direct SQL or dedicated repositories
Pre-configured Messenger Handlers using the #[AsMessageHandler] attribute
21 GitHub stars
Separate Command and Query buses with specialized middleware configuration

Use Cases

Optimizing read-heavy performance by implementing dedicated read models alongside domain entities
Refactoring monolithic controllers into decoupled, testable command and query handlers
Building complex enterprise-grade Symfony applications that require a clean separation of concerns