We will use RabbitMQ, which is free and super easy to setup. We want a Message Queue (MQ) so this project to support horizontal scaling. There are a variety of options for MQ (RabbitMQ, ZeroMQ, MSMQ, NServiceBus, Azure Service Bus), some free and open source, some commercial and fully featured with support options.We won’t need distributed transactions ( This article has some excellent information related to service bus design).We will not be running any long processing background tasks (perhaps in a future post I will show an example of this).We want SignalRChat to be horizontally scalable, and users can chat to each other, even though they might be hosted on different servers (an example of horizontal scaling).
Our goal is to have our message flow look like: So you may need to adjust your design depending on your system limits and design requirements. IIS can and will behave unpredictably with requests that take longer than 30 seconds). But if the generation can take over 30 seconds (minutes, or even hours), you definitely need to think about processing the request outside of the web server process (eg. Typically, as a developer your first inclination would be to generate the report on the fly with each HTTP request. The most simple example would be if you have a webpage that is used to generate a report. I plan to make future posts which will leverage more features of the service bus. They can do a lot more, but we will just be exploring a very simple usage scenario. Without going into too much detail (you can find many websites with more thorough explanations), a service bus lets you send messages (which contain a payload/instruction) for out-of-process handling. We will build on this project made in a previous post. In this tutorial we will add a service bus using MassTransit.
0 kommentar(er)
