RabbitMQ, an open source message broker, is part of Pivotal Software, a VMware company acquired in 2019, and supports message queue, multiple messaging protocols, and more.
RabbitMQ is available open source, however VMware also offers a range of commercial services for RabbitMQ; these are available as part of the Pivotal App Suite.
N/A
Ubuntu
Score 8.8 out of 10
N/A
Ubuntu Linux is a Linux-based operating system for personal computers, tablets and smartphones. There is also a Server version which is used on physical or virtual servers in the data center.
It is highly recommended that if you have microservices architecture and if you want to solve 2 phase commit issue, you should use RabbitMQ for communication between microservices. It is a quick and reliable mode of communication between microservices. It is also helpful if you want to implement a job and worker mechanism. You can push the jobs into RabbitMQ and that will be sent to the consumer. It is highly reliable so you won't miss any jobs and you can also implement a retry of jobs with the dead letter queue feature. It will be also helpful in time-consuming API. You can put time-consuming items into a queue so they will be processed later and your API will be quick.
If somebody whishes to be an IT professional, learning the basics of Linux is amust. Ubuntu [Linux] is one of the most beginner-friendly, widely supported, easy-to-use-relative-to-the-fact-that-its-still-linux OS on the market. As somebody who learned the basics of UNIX/LINUX on Ubuntu, it was a very good experience. It is customizable, has a lot of improvements over the years, and live up to be a viable alternative to any modern OS in 2021 as well.
What RabbitMQ does well is what it's advertised to do. It is good at providing lots of high volume, high availability queue. We've seen it handle upwards of 10 million messages in its queues, spread out over 200 queues before its publish/consume rates dipped. So yeah, it can definitely handle a lot of messages and a lot of queues. Depending on the size of the machine RabbitMQ is running on, I'm sure it can handle more.
Decent number of plugins! Want a plugin that gives you an interface to view all the queues and see their publish/consume rates? Yes, there's one for that. Want a plugin to "shovel" messages from one queue to another in an emergency? Check. Want a plugin that does extra logging for all the messages received? Got you covered!
Lots of configuration possibilities. We've tuned over 100 settings over the past year to get the performance and reliability just right. This could be a downside though--it's pretty confusing and some settings were hard to understand.
It breaks communication if we don't acknowledge early. In some cases our work items are time consuming that will take a time and in that scenario we are getting errors that RabbitMQ broke the channel. It will be good if RabbitMQ provides two acknowledgements, one is for that it has been received at client side and second ack is client is completed the processing part.
RabbitMQ is very easy to configure for all supported languages (Python, Java, etc.). I have personally used it on Raspberry Pi devices via a Flask Python API as well as in Java applications. I was able to learn it quickly and now have full mastery of it. I highly recommend it for any IoT project.
I gave it 10 out of 10 because it allows me to do the work I need on a server, such as running a website and database, and making developments. In addition, thanks to its easy and useful interface during installation, it can be easily installed. In addition, thanks to its easily accessible documents, when a problem occurs, it can be solved easily and quickly.
I gave it a 10 but we do not have a support contract with any company for RabbitMQ so there is no official support in that regard. However, there is a community and questions asked on StackOverflow or any other major question and answer site will usually get a response.
We did not use the managed commercial support, but instead relied on community forums and official documentation. Ubuntu is very well documented across both instructional documentation from the developers themselves as well as informal support forums [ServerFault, YCombinator, Reddit]. It's easy enough to find an answer to any question you may have
RabbitMQ has a few advantages over Azure Service Bus 1) RMQ handles substantially larger files - ASB tops out at 100MB, we use RabbitMQfor files over 200MB 2) RabbitMQ can be easily setup on prem - Azure Service Bus is cloud only 3) RabbitMQ exchanges are easier to configure over ASB subscriptions ASB has a few advantages too 1) Cloud based - just a few mouse clicks and you're up and running
Windows 10: Expensive, with more security problems, more difficult to keep updated and less variety of free / open source applications. Its use encourages bad information security practices. OpenSuse Linux: A different distribution at source (Suse Linux), use of rpm packages (with fewer repositories and incompatible with Ubuntu Linux dpkg packages), and whose main objective is to be a "testing ground" for its paid version / professional, SUSE enterprise Linux.
Positive: we don't need to keep way too many backend machines around to deal with bursts because RabbitMQ can absorb and buffer bursts long enough to let an understaffed set of backend services to catch up on processing. Hard to put a number to it but we probably save $5k a month having fewer machines around.
Negative: we've got many angry customers due to queues suddenly disappearing and dropping our messages when we try to publish to them afterward. Ideally, RabbitMQ should warn the user when queues expire due to inactivity but it doesn't, and due to our own bugs we've lost a lot of customer data as a result.
Positive: makes decoupling the web and API services from the deeper backend services easier by providing queues as an interface. This allowed us to split up our teams and have them develop independently of each other, speeding up software development.
Systems administration with Ubuntu is easy with little deep knowledge about it. Docs and community publications are great resources for any task you need to perform on any Ubuntu server and the organization can save several salaries of specialized sys admins in favor of more active roles.
Having been an Ubuntu user for many years personally, setting up new Ubuntu servers on my organization came with zero cost for me. I just deployed one instance from my hosting/cloud provider and started working right after it was running, no need to ask support or hire new staff for these tasks.
Replacing paid options with Ubuntu have also saved thousands of dollars on Windows Server licenses. I've migrated Windows/SQL Server based systems to Ubuntu/MySQL/PostgreSQL several times during my career and saved about USD 5000/year in licenses to many of them.
