For instance if you run just the website in the sample project, from the blog post you linked. However, from what I can tell, I am in the minority. alexeyzimarev The GetSendEndpoint(uri) and corrisponding Send(.) do not allow you to send directly to a queue. If you just publish only, you could have gotten it without any other consumer or processing knowing or being modified. Later when someone else needs it, you have to modify the consumer of UpdateCustomer to send the CustomerUpdated message. It can send a message and wait for the response, and it does all the coordination for you. So, you build the above and do not create the CustomerUpdated message. It can do the asynchronous, but it can also be the request response type patterns because you can do those over messaging. My issue with that is you are not going to over-engineer your solution and publish all kinds of messages 'just in case' someone needs to know about it later.
When finished processing, it would publish a 'CustomerUpdated' message that anyone can listen to. So, in the above, they would create an UpdateCustomer message and 'send' it. Some people use 'send' as commands and 'publish' as events. MassTransit also offers a Request and Response.
When using publish, the message is broadcast to many consumers.
SEND A MESSAGE USING MASSTRANSIT FULL
MassTransit uses the full type name, including the namespace, for message contracts. Messages should only consist of properties, methods and other behavior should not be included. A message can be defined using a record, class, or interface. a queue and a single consumer subscribes to this queue. In MassTransit, a message contract is defined code first by creating a. A message is delivered to a specific endpoint. For instance if we want to use a 'UpdateCustomer' message as a send.then later you want something else to listen and act on that same 'UpdateCustomer' message - you cannot do it. From my understanding, there are three ways that you can send messages using MassTransit. If you 'publish' a message then anyone can build something that listens for that and see it. If you 'send' a message then only one queue subscriber will ever see it.
0 kommentar(er)
