If you need more capabilities than I'd consider Redis and use it for all sorts of other things such as a cache. In my taste, you should go with a minialistic approach and try to avoid either of them if you can, especially if your architecture does not fall nicely into event sourcing. Kafka nowadays is much more than a distributed message broker. 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. ![]() 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. You can feel confident that our case will be handled with the utmost expertise and professionalism.MassTransit vs RabbitMQ: What are the differences? Cannot send messages from unit test using in-memory MassTransit MessageLockLostException on unhandled exception in combination with ConfigureDeadLetterQueueErrorTransport for MassTransit on Azure Service Bus MassTransit - random mediator response not consumed MassTransit failes to process job MassTransit. Our legal team will go to work to build your case and take on the insurance company on your behalf. Petersburg-Clearwater area, including breaking news, public safety, crime, health, hurricanes and weather, politics, the environment. Represent you in court if you decide to file a lawsuit.Fight for a fair settlement from the insurance company. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |