Need advice about which tool to choose?Ask the StackShare community!
CloudAMQP vs Compose: What are the differences?
CloudAMQP: RabbitMQ as a Service. Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms; Compose: We host databases for busy devs: production-ready, cloud-hosted, open source. Compose makes it easy to spin up multiple open source databases with just one click. Deploy MongoDB for production, take Redis out for a performance test drive, or spin up RethinkDB in development before rolling it out to production.
CloudAMQP can be classified as a tool in the "Message Queue" category, while Compose is grouped under "MongoDB Hosting".
Some of the features offered by CloudAMQP are:
- Support - 24/7 support, via email, chat and phone.
- Real time metrics and alarms - Get notified in advanced when your queues are growing faster than you're consuming them, when you're servers are over loaded etc. and take action before it becomes a problem.
- Auto-healing - Our monitoring systems automatically detects and fixes a lot of problems such as kernel bugs, auto-restarts, RabbitMQ/Erlang version upgrades etc.
On the other hand, Compose provides the following key features:
- One click, production-ready, cloud hosted MongoDB, Redis, Elasticsearch, PostgreSQL and RethinkDB, with additional databases in beta.
Every deployment features: database autoscaling based on data size usage - private VLAN, IP whitelisting, SSL, full-stack monitoring, custom alerts - HA and fault tolerance with automatic failover
"Some of the best customer support you'll ever find" is the top reason why over 3 developers like CloudAMQP, while over 41 developers mention "Simple to set up" as the leading cause for choosing Compose.
According to the StackShare community, Compose has a broader approval, being mentioned in 82 company stacks & 19 developers stacks; compared to CloudAMQP, which is listed in 12 company stacks and 5 developer stacks.
In addition to being a lot cheaper, Google Cloud Pub/Sub allowed us to not worry about maintaining any more infrastructure that needed.
We moved from a self-hosted RabbitMQ over to CloudAMQP and decided that since we use GCP anyway, why not try their managed PubSub?
It is one of the better decisions that we made, and we can just focus about building more important stuff!
Pros of CloudAMQP
- Some of the best customer support you'll ever find4
- Easy to provision3
Pros of Compose
- Simple to set up42
- One-click mongodb32
- Automated Backups29
- Designed to scale23
- Easy interface21
- Fast and Simple13
- Real-Time Monitoring10
- Fastest MongoDB Available7
- Great Design6
- REST API6
- Easy to set up4
- Free for testing3
- Geospatial support3
- Elasticsearch2
- Heroku Add-on2
- Automated Health Checks1
- Email Support1
- Query Logs1