What is messaging

You may also like...

4 Responses

  1. Jean-Paul Smit says:

    Interesting article. Can you say anything about the performance hit you get with this dynamic behavior? Can you elaborate on the experience you have with this approach and if this is considered to be a best practice from your point of view?

  2. Dennis van der Stelt says:

    Of course the reflection over assemblies and classes causes a performance hit, but you can store the information you get from it in a collection and keep it in memory. That way you only have to do it once.

    When you are able to work with this, it certainly is a great way to send messages. As said, it decouples, which is almost always a good thing. From experience it’s very clear what is happening (SomeMessage, SomeHandler, OtherMessage, OtherHandler) and very maintainable.

    Of course you cannot always do messaging, as you also need other forms of communication. An easy example is request/response, where you wait for a reply. Using messages and queues is much harder, if not impossible than.

  3. Jean-Paul Smit says:

    Regarding the WCF approach with the message handler, is this your standard way of work if you need to develop a service?

  4. Dennis van der Stelt says:

    Nope, we almost always use nServiceBus for this.

Click on a tab to select how you'd like to leave your comment

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>