CQRS pattern is now live on DarkPool's NestJS backend via @nestjs/cqrs. → CommandBus handles writes • CreateOrderCommand • CancelOrderCommand • FillOrdersCommand → QueryBus handles reads • GetOrdersQuery • GetOrderStatsQuery • GetActiveOrdersByGpuQuery • GetRecentSettlementsQuery → OrdersService refactored to a thin facade delegating to bus handlers → Settlement controller queries separated into dedicated QueryHandlers → Read path no longer contends with write path → Zero API breaking changes built on @base • live on @baseapp github.com/DarkPoolBase/Dark… darkpoolbase.org

Ugh. Actions are not Commands and certainly not a CommandBus. Actions evolved from Laravel's "self handling commands" which was an intentional step back from the CommandBus and traditional Commands, both of which had been in the software pattern language long before Laravel. History is important.

Me está discutiendo que no quiere usar el Commandbus....

True. All you need is a BaseCommand, BaseHandler and a CommandBus. Go crazy and add a BaseValidator. Duh.

We'll write one for CommandBus::dispatch() calls. It will look at the type of the THandler from the passed command class, look at its __invoke() method, and return that:

So with everything above, PHPStan is now able to infer that CommandBus::dispatch() called with Command1Input will return Command1Result. Now onto propagating thrown exceptions from the handler. For that we need to write a custom DynamicMethodThrowTypeExtension.

CommandBus::dispatch() should be able to infer the returned result type from the command class passed as argument. The "*" in place of handler type is so-called star projection from recent call-site variance feature. It means we don't want to limit the handler type, any will do.

What's happening here is that all my command handlers are built to work with data from commands — simple PHP objects. They modify in-memory objects (the read model), which only gets persisted at the very last moment. Skip that last part during testing (could be a commandbus middleware that's disabeld), and you don't need a database dependency for most of your tests. It's all in-memory data that you can perform assertions on directly.

Joindre l'utile et le ludique : pour mon apprentissage je vulgarise des concepts techniques au travers de schémas 🎨. Voici par exemple ma vision du #commandBus avec #Symfony #Messenger 📨, et son worker aux p'tits bras 💪

In our hexagonal #laravel application, we have 192 tests, 2444 assertions and it takes 2.8 seconds to Unit/Functional test the entire system top to bottom This includes - Unit Tests - API tests - Internal functional tests on CommandBus - Internal function tests on Repositories

I found this awesome link, bringing back CommandBus into Laravel dev.to/mtk3d/restore-missing…

🚨 Which design pattern will help you to handle a use case? How to ensure user inputs are valid? How to apply for user permission? I wrote a bunch of blogs to explain that in the thread 🧵👇 #commandBus #Software #commandHanler #designerPattern #middleware

Currently i am working hard to improve the Symfony Messenger Integration for TYPO3 even further. I.e. sending emails via the Messenger. Btw. the Messenger is not only about async functionality but can also be used i.e. as a CommandBus. Check it github.com/sabbelasichon/t3_…

In 2016 we implemented a CommandBus in .net for our own new architecture for the web (Starlogic). Today, we still build on this architecture for our cloud services at @bluestarplan in Net Core. Some blogposts may come up soon.

I can also recommend the League CommandBus. Which also supports middleware for transactions, logging etc. tactician.thephpleague.com

🚌 CommandBus = Command Chain of Responsibility En el curso de Patrones de comportamiento, nos estamos divirtiendo mucho combinándo los patrones! ¡Ya tienes disponible el primer bloque! 👇 pro.codely.com/library/patro…

🚩🚀Bus de comandos en @laravelphp ¿Sabes como utilizar el despachador de tareas de Laravel? Os muestro un ejemplo para crear una implementación de CommandBus síncrono. 🔴Tener un bus de comandos y de queries es muy importante a la hora de implementar una aplicación con DDD.

Actions, using dependency injection, or even CommandBus would be a significant improvement here. Traits create coupling, and technical debt.

This creates seriously difficult coupling. There is a better way, dependency injection. Inject additional dependencies into your model/repository/command class. CommandBus pattern would really help here, as it gives a central point of execution and maintenance All the best 👍

I must say it out loud - PHP 8.1 is just great. It simplifies a lot of things and thanks to its new features, we can make a simple CommandBus implementation that looks as awesome as this one: gist.github.com/RadnoK/a1024…💙