Artwork

Content provided by Udi Dahan. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Udi Dahan or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

[Podcast] Message Priority – You Aren’t Gonna Need It

 
Share
 

Manage episode 65045178 series 63841
Content provided by Udi Dahan. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Udi Dahan or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

In this podcast we’ll be discussing the issues around supporting different kinds of service-level agreements in an SOA, and how using message prioritization helps and hurts. We’ll also be looking at alternative solutions more distributed in nature,which make use of specific deployment and configuration schemes that result in a more robust system.

Symon asks:

Hi Udi,

I don’t know if this is really an NServiceBus question or a more general architecture question, so if you want to treat it as an Ask Udi question feel free. 🙂 My question is about handling message prioritization between services in an SOA architecture using an ESB- in this case NServiceBus.

We’ve been running along nicely getting the hang of using the NServiceBus but have just hit a point in our application where it’s become clear that we’re going to need to prioritize messages between services according to an arbitrary set of rules. To that end we’ve created a “controller” that determines a message’s priority according to a set of rules and that controller should forward the message to other services for handling according to that priority. Where we’re stuck is figuring out the best way to handle the prioritization of the forwarded message.

We touched on the idea of having several endpoints representing low, medium or high priority and shunting the message to the appropriate endpoint, however since the receiving service consists of multiple workers located on other machines we need to have a dispatcher for each of these endpoints. Since we’re using MSMQ this seems to be causing an explosion of queues and the solution seems to require a lot of overhead in terms of set up, but it *does* look like it might be flexible as long as we come up with a smart dispatcher.

Is this an “ideal” way to handle message prioritization? I know there is a notion of priority in MSMQ messages, but this isn’t exposed in NServiceBus as far as I can tell.

Any suggestions?

Cheers,

Symon

Download

Download via the Dr. Dobb’s site

Or download directly here.

Additional References

Want more?

Check out the “Ask Udi” archives.

Got a question?

Send Udi your question to answer on the show.

  continue reading

21 episodes

Artwork
iconShare
 
Manage episode 65045178 series 63841
Content provided by Udi Dahan. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Udi Dahan or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

In this podcast we’ll be discussing the issues around supporting different kinds of service-level agreements in an SOA, and how using message prioritization helps and hurts. We’ll also be looking at alternative solutions more distributed in nature,which make use of specific deployment and configuration schemes that result in a more robust system.

Symon asks:

Hi Udi,

I don’t know if this is really an NServiceBus question or a more general architecture question, so if you want to treat it as an Ask Udi question feel free. 🙂 My question is about handling message prioritization between services in an SOA architecture using an ESB- in this case NServiceBus.

We’ve been running along nicely getting the hang of using the NServiceBus but have just hit a point in our application where it’s become clear that we’re going to need to prioritize messages between services according to an arbitrary set of rules. To that end we’ve created a “controller” that determines a message’s priority according to a set of rules and that controller should forward the message to other services for handling according to that priority. Where we’re stuck is figuring out the best way to handle the prioritization of the forwarded message.

We touched on the idea of having several endpoints representing low, medium or high priority and shunting the message to the appropriate endpoint, however since the receiving service consists of multiple workers located on other machines we need to have a dispatcher for each of these endpoints. Since we’re using MSMQ this seems to be causing an explosion of queues and the solution seems to require a lot of overhead in terms of set up, but it *does* look like it might be flexible as long as we come up with a smart dispatcher.

Is this an “ideal” way to handle message prioritization? I know there is a notion of priority in MSMQ messages, but this isn’t exposed in NServiceBus as far as I can tell.

Any suggestions?

Cheers,

Symon

Download

Download via the Dr. Dobb’s site

Or download directly here.

Additional References

Want more?

Check out the “Ask Udi” archives.

Got a question?

Send Udi your question to answer on the show.

  continue reading

21 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide