We have compiled MediatR, RabbitMQ, NServiceBus and CQRS for you – see how these technologies are prepared and learn about their most important ones.
MediatR is a library that enables the implementation of the Mediator design pattern in .NET Core applications. The pattern allows you to separate business logic from usable presentation. MediatR allows access to parts of the system without directly connecting them to each other. Benefits: Separation of business logic from the functional presentation of extension testing
RabbitMQ to the broker, which enables the transfer of messages between applications or system components. RabbitMQ is very easy to use. It supports multiple protocols including AMQP and MQTT. Benefits: Scalability High availability Support for multiple protocols
NServiceBus to a library that enables the development of distribution systems in .NET Core. NServiceBus provides mechanisms for error handling, scalability, and asynchronous processing. It supports various protocols including MSMQ, RabbitMQ, and Azure Service Bus. Benefits: Scalability High availability Asynchronous processing supporting various protocols
CQRS is a design marking that is responsible for clearing the read-write penalty in the application. This technology uses models for queries and functions. The request model is available for reading data, the model for reading and updating data.
Benefits: Revocation of reading of utility data. Scalability of the ability to read and write data
Short summary:
MediatR, RabbitMQ, NServiceBus and CQRS to technologies that can be specified in different options: Mediator is a disclosure for revealing business logic from presentation. RabbitMQ is a good solution if you want to use distributed systems. NServiceBus is suitable for error handling, asynchronous processing and scaling. Otherwise CQRS is the perfect solution if you want to get read from write from it.
Maciej Cebula