We installed VMware RabbitMQ on a local computer. We are currently using Docker and Kubernetes for deployment in our local environment. It was relatively easy to deploy compared to an on-premise system.

The solution can be a bit challenging to handle. Not every configuration and deployment works seamlessly. It depends on the project team and compatibility, but is relatively easy to use.

The solution's installation process was straightforward, especially if you have good skills in installing software and a good command of Linux. Once the Bandit software is downloaded and extracted, the installation is completed.

After that, accessing the admin interface allows for a user-friendly GUI experience. The deployment process took around half an hour. 

We have a private cloud infrastructure using VMware, which means our servers are running on-premises and are owned by our company. We have a limited number of servers running the solution.

Specifically, we have one primary server and one secondary server without implementing clustering. Replicating these two servers is sufficient for our workload, and they can be installed by a single system administrator in just half an hour without any issues, provided they have DPU-installed Linux available.

Overall, I would rate the setup experience as nine out of ten.

The initial setup is complex. The product is deployed on the cloud. The configuration and setup are pretty complicated.

The initial setup is complex. It is difficult to find any documentation explaining the process. I deploy the code on the server using Jenkins.

VMware RabbitMQ's installation is easy. However, it doesn't come with any manuals. 

Thanks to Pivotal Cloud Foundry, initial setup was straightforward. We simply created a new RabbitMQ service, obtained credentials for the queue and started developing.

It was bundled with PCF, so it was never a problem for us.

The non-sharded/clustered setup is very easy and straightforward. The clustered solution setup is much more complicated.

These days the initial setup is moderately complex because it uses a technology that is worldwide, Erlang, which is obscure. You have to install Erlang first and that is moderately difficult. Deployment takes about a day. 

The initial setup was simple. The first time I installed it, I installed it on Windows. For me, it took about one hour. If a user was facing a few problems, I'd say it could take up to two hours. Typically it's pretty quick to set up because the recommendations are pretty good.

The initial setup was fairly complex. Installation was not difficult, but configuration of the server itself took some work.

I ended up creating code that does the RabbitMQ setup based on a configuration file. This eased the setup dramatically. I also set up a central LDAP server for authentication, which helped. Otherwise, configuration of RabbitMQ was not very straightforward.

The complexity of the setup depends on the scope of the implementation. For a single node, the initial setup is very easy. On the other hand, for setting up RabbitMQ with a cluster, you really have to know what you're doing.

The setup was straightforward. We are implementing using Node.js and the module we are using was easy to use.

Initial setup was relatively simple and then we were able to grow into the product by using more of the features.

The setup was easy enough, once we had done proper research before the implementation.

I was there when the solution was initially implemented and, from what I recall, it took half a year. 

It was completely new. No one knew anything about it. However, we knew that we had to do something to improve the communication between departments. It was a good solution. That said, it took a long time before everyone understood how it works.

We had a few dedicated people who liked the idea of Rabbit and implemented it. It took a while for the rest of the company to get behind them and learn how to do it.

There are one or two people at any given time available to handle any type of maintenance responsibilities.

The installation is very simple and elegant, and we love the graphics. It lets us see exactly what is happening with the ability to start the queue, stop the queue, consume messages on the queue. This is a huge help.

The initial setup was straightforward. The online documentation was adequate and there is minimal initial configuration required to get up and running.

After that, it is simply a matter of experimentation with the various features and learning as you go.

The initial setup was simple for my applications, but I have not used RabbitMQ on a complex project that would require clusters of servers.

Simple. We followed the tutorial about RabbitMQ with Python.

It was a very simple setup. We had some issues with the home folder being on a non-standard system drive (The location of the RMQ cookie was changed.)

Just enter this command: $ apt-get install rabbitmq-server

Initial setup was decently elaborate. The documentation is good but there are a few quirks in the case of Windows. The RabbitMQ processes would be running but the status would show that it is down. The solution was to stop and restart the process. This only happened on Windows.

The setup is easy.

The setup was okay, but there are some configurations that one needs to do by oneself. There are many dependencies as well.

The setup was pretty straightforward.

It is not complex.

However, if you try sharding or cluster, it is just a little complex because of Erlang.

The initial setup is not very complex. We just needed to set up several broker instances running on different physical nodes to prevent unavailability. When we needed to add more nodes for more data and queues at a later time, it created a bit of load imbalance issues.

The initial deployment was quite easy. It took less than half an hour to get it up and running.

The initial setup was very easy and takes about five minutes to install.

It is very simple to set up for basic usage. Clustering is a bit more complex, but it is also easy to do.

The initial setup is quite straightforward. It can be done within a few hours. 

We are a container shop and the only issues during setup were around proper clustering and configuring the application to use it.

It involved more of research as how to use RabbitMQ. For clustering, it was little bit complex but I was able to follow the documentation provided.