Our main use case for CloudAMQP is that we are using it for RabbitMQ operations as a message broker, with CloudAMQP managing RabbitMQ. Apart from that, we use it for microservice communication. In our use case, there are multiple consumers and applications. From the application side, a payload is uploaded, and multiple consumers communicate with this JSON, which is directly related to that particular application. We also use the RabbitMQ queue to process this data with the help of a synchronous technique.

We have a multiple microservice-based architecture, and a quick specific example of how CloudAMQP fits into our workflow is that we have different operations involving order management and notification management, along with transactions related to payment. Our application sends the event, and different microservices consume that particular data. CloudAMQP is able to handle a huge amount of data and can manage these operations automatically, ensuring there is no spike and no lag inside the application.

The best features CloudAMQP offers include its ability to handle load efficiently. Without it, if there is a lack of requests coming from multiple consumers, it stores the data in the queue, and the lag will clear after consumption from the consumer side, ensuring no messages drop from CloudAMQP. Additionally, it can run tasks in the background so that it does not block any user requests. CloudAMQP is able to handle the load, and if I want to scale, I can scale the RabbitMQ nodes without any downtime.

CloudAMQP has impacted our organization positively because it can handle a huge amount of data. I can have multiple RabbitMQ queues inside CloudAMQP and, as per my plan, purchase multiple queues that offer different capabilities. For example, the Tough Tiger plan allows sending a maximum of ten million messages per month with simultaneous connections of one hundred connections per queue, ensuring no traffic loss. For heavy environments, I can opt for Big Bunny queues, where I can handle one lakh messages per second if there is a huge amount of traffic. Additionally, I have a dedicated RabbitMQ broker as per my requirement, and according to my needs in CloudAMQP, there are different queue plans which I can select accordingly.

CloudAMQP can be improved, as sometimes while upgrading, for instance, if I am running a Big Bunny cluster and want to upgrade to Happy Hour, there is a lag or slowness while upgrading from one queue to another.

Apart from the upgrade lag, everything is working fine with excellent customer support. Regarding pricing, there are lots of pricing plans in CloudAMQP, allowing me to purchase based on my requirements.

I have been using CloudAMQP for around three years.

In my experience, CloudAMQP is very much stable.

The scalability of CloudAMQP is very much effective. I can directly scale the system with the UI.

My experience with scaling RabbitMQ nodes is positive. From the CloudAMQP UI, I can scale it as per my load and requirements, and I can manage it easily.

I would add that you can scale it by running multiple replicas, and if there is any traffic spike, it will handle the load as per your replica of your RabbitMQ queue, making it very much beneficial.

The customer support is excellent. I would rate the customer support on a scale of one to ten as eight out of ten.

I did not previously use a different solution, as this is the first one I am using.

My experience with pricing, setup cost, and licensing is that it operates on a private cloud, not on-premises.

Since using CloudAMQP, my organization has seen a very significant return on investment because there is no data loss, and I can recover the system timely. In logistic operations, there are multiple issues; if my system is down, it causes transaction-related loss and revenue loss to the organization. There is a return on investment by using CloudAMQP.

I have seen a return on investment, as it helps in saving money and time.

Before choosing CloudAMQP, I evaluated other options, specifically Kafka, but as per my use case, CloudAMQP fits well.

My advice for others looking into using CloudAMQP is that if you are choosing any message broker, you can go directly to CloudAMQP. However, before making a choice, at least check their plans according to your use case and do not blindly choose any plan. I would rate this product ten out of ten.

CloudAMQP is mainly used for message queuing and asynchronous communication between applications and services.

We have a hardware device which is made up of circuits, and it will communicate with the real-time dispenser unit in the fuel station. Once the data is taken from the fuel pump, it will transmit to the server. From the server, it will be queued in the AMQP and it will be displayed in the front end.

CloudAMQP is deployed in our organization on our private cloud.

The best features that CloudAMQP offers include handling server setup, RabbitMQ installations, upgrades, patching, maintenance, scaling, and backup. It is a fully managed RabbitMQ, allowing easy scaling without any downtime.

CloudAMQP offers strong monitoring and alerting features that make managing the RabbitMQ environment much easier, providing real-time visibility into the queues, messaging rates, consumers, and memory usage through an easy-to-use dashboard.

After using CloudAMQP, our efficiency has increased, and the data which is transferring from the fuel station has become easier and faster to communicate with our front-end application. The data which is queued in RabbitMQ is providing the fastest response to the front-end application.

CloudAMQP can be improved in a few ways, such as lowering the pricing at scale and keeping the pricing structure simpler. It should also have a better beginner experience, improvements in UI and UX, and we would appreciate more advanced analytics.

I have been using CloudAMQP for one and a half years.

CloudAMQP is stable.

CloudAMQP's scalability is good.

We have never needed to reach out to customer support.

The setup cost is low because the platform is fully managed, so teams don't need to spend much on infrastructure or DevOps resources. The setup process is quick and developer-friendly, often taking only a few minutes to get running.

I have seen a return on investment with time saved.

CloudAMQP has a flexible pricing model with both free and paid plans that make it easy to start small and scale later.

Licensing is subscription-based with monthly billing, and while pricing can become expensive at higher scales, many teams feel the operational convenience and reliability justify the cost of production workloads.

If you are considering CloudAMQP, my advice is to start with a small plan and learn RabbitMQ fundamentals such as queues, exchange, and routing keys early. CloudAMQP is excellent for microservices, background jobs, and event-driven systems because it reduces infrastructure and maintenance efforts significantly. Make good use of its monitoring and alerting features from the beginning and design your queues carefully for better scalability and performance. I would rate this product a ten out of ten.