I like your implementation. I have one concern to share with you. Don't you think that the UserInterface for instance is violating the idea of CQRS in common? Because in CQRS you are splitting your writes from your reads and in this case, your repository might only have to have one read method to load the aggregate by its ID while it case persist the aggregate
Born before Internet, started as "webmaster", now supporting people mastering it.
I was shaped by XP methodology & DDD architectures. Open source enthusiast.
Hi, thank you for a nice post. Also you can find my implementation of DDD/CQRS there
github.com/ferrius/ddd-cqrs-example
I like your implementation. I have one concern to share with you. Don't you think that the UserInterface for instance is violating the idea of CQRS in common? Because in CQRS you are splitting your writes from your reads and in this case, your repository might only have to have one read method to load the aggregate by its ID while it case persist the aggregate
I checked, and it looks clean, here's a DDD / CQRS / ES with Symfony/Doctrine & SQL as event store
github.com/ludofleury/blackflag