In most messaging systems I’ve worked with (synchronous or asynchronous), there are three general types of messages that arise:
Queries can be thought of as a special kind of command where I ask for something and get a result. When moving from imperative languages to messaging patterns, it can be a bit of a leap to think in terms of interacting via messages, instead of just interacting with objects directly. In introducing messaging to developers, it’s common to have a bit of trouble making sure interactions match the message and naming semantics you intend.
In NServiceBus, we have three major means of telling NServiceBus to send a message:
Each of these in turn corresponds to Commands, Replies, and Events, respectively. But we need to go one step further, and ensure that the names of our messages matches the intent of our communication. When names don’t match the semantics of an interaction, it’s a design smell and an indication that something in your design of interactions has gone awry.
One easy way to verify semantics is to simply check the naming of the message. Each message type has a very particular design in its name to be as explicit as possible about what the nature of the message and interaction is,
- Command: Imperative verb
- Reply: Noun
- Event: Past-tense verb (past simple, to be specific)
- Command: RegisterCustomer
- Reply: RegisterCustomerResult
- Event: CustomerRegistered
Replies often describe the result of a command, and are usually tied 1:1 with a specific command. Or, a more general result can be used.
So if you Bus.Send a message that is worded in past tense, or Bus.Publish a message that seems rather bossy (Bus.Publish<UpdateCache>) then your interaction and semantics are off.
Next up – ownership.
Post Footer automatically generated by Add Post Footer Plugin for wordpress.