From 4ef97fe24236a94b7c636ae1493bbfca6cc4aae1 Mon Sep 17 00:00:00 2001 From: Udi Dahan Date: Tue, 1 Nov 2022 15:14:09 +0200 Subject: [PATCH] Added link to RabbitMQ site + link to NSB in "additional resources" --- .../rabbitmq-event-bus-development-test-environment.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/architecture/microservices/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment.md b/docs/architecture/microservices/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment.md index 8102383fbe5c9..8791a9725ef0d 100644 --- a/docs/architecture/microservices/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment.md +++ b/docs/architecture/microservices/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment.md @@ -7,7 +7,7 @@ ms.date: 01/13/2021 [!INCLUDE [download-alert](../includes/download-alert.md)] -We should start by saying that if you create your custom event bus based on RabbitMQ running in a container, as the eShopOnContainers application does, it should be used only for your development and test environments. Don't use it for your production environment, unless you are building it as a part of a production-ready service bus. A simple custom event bus might be missing many production-ready critical features that a commercial service bus has. +We should start by saying that if you create your custom event bus based on [RabbitMQ](https://www.rabbitmq.com/) running in a container, as the eShopOnContainers application does, it should be used only for your development and test environments. Don't use it for your production environment, unless you are building it as a part of a production-ready service bus as described in the [Additional resources section below](/dotnet/architecture/microservices/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment#additional-resources). A simple custom event bus might be missing many production-ready critical features that a commercial service bus has. One of the event bus custom implementations in eShopOnContainers is basically a library using the RabbitMQ API. (There's another implementation based on Azure Service Bus.) @@ -112,13 +112,16 @@ For production scenarios check the additional resources below, specific for Rabb A production-ready solution with support for RabbitMQ. +- **NServiceBus** - Fully-supported commercial service bus with advanced management and monitoring tooling for .NET \ + + - **EasyNetQ** - Open Source .NET API client for RabbitMQ \ -- **MassTransit** \ +- **MassTransit** - Free, open-source distributed application framework for .NET \ -- **Rebus** - Open source .NET Service Bus +- **Rebus** - Open source .NET Service Bus \ > [!div class="step-by-step"]