Yes, so many buzzwords together - I admit.
The difference is replacing Commnad/Query with events. Replacing Imperative with Reactive.
Did you read the whole post or you were put off by the buzzwords?
The difference is replacing Commnad/Query with events. Replacing Imperative with Reactive.
Did you read the whole post or you were put off by the buzzwords?
Command/Query pattern is an imeplementation concern. The architectural pattern that backs it up isn't necessarily related (for example event sourcing). At that point it isn't imperative so why is this different? It just appears to be fragmenting lots of concerns into even smaller ones which are vastly more complicated to debug and manage.
The bold highlighted text of: "in a reactive actor system, each actor only knows about its own Step and what itself does and has no clue about the next steps or the rest of the system"
Isn't that the same for a message channel but without a transactional guarantee? (going back a decade or more to EIP).