#MASSTRANSIT AND SIGNALR SOFTWARE#

But also note that Redis is not a pure message broker (at time of writing) but more of a general purpose in-memory key-value store. I have a good past experience in terms of manageability/devops of the above options with Kafka and Redis, not so much with RabbitMQ.

Do you need Pub/Sub or Push/Pull? Is queuing of messages enough or would you need querying or filtering of messages before consumption? Also, someone would have to manage these brokers (unless using managed, cloud provider based solution), automate their deployment, someone would need to take care of backups, clustering if needed, disaster recovery, etc.

Why are you considering event-sourcing architecture using Message Brokers such as the above? Won't a simple REST service based arch suffice? Read about CQRS and the problems it entails (state vs command impedance for example). I think something is missing here and you should consider answering it to yourself. Here's a link to RabbitMQ's open source repository on GitHub. RabbitMQ is an open source tool with 6.07K GitHub stars and 1.85K GitHub forks. On the other hand, RabbitMQ provides the following key features: Some of the features offered by MassTransit are: MassTransit and RabbitMQ belong to 'Message Queue' category of the tech stack. RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

#MASSTRANSIT AND SIGNALR SOFTWARE#

NET-based Enterprise Service Bus software that helps Microsoft developers route messages over MSMQ, RabbitMQ, TIBCO and ActiveMQ service busses, with native support for MSMQ and RabbitMQ RabbitMQ: A messaging broker - an intermediary for messaging. MassTransit is free software/open-source. MassTransit: Lightweight message bus for creating distributed applications. MassTransit vs RabbitMQ: What are the differences?

Masstransit and signalr