CloudAMQP vs DistributedLog: What are the differences?
What is CloudAMQP? RabbitMQ as a Service. Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms.
What is DistributedLog? High-performance replicated log service, by Twitter. DistributedLog (DL) is a high-performance, replicated log service, offering durability, replication and strong consistency as essentials for building reliable distributed systems.
CloudAMQP and DistributedLog can be categorized as "Message Queue" tools.
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, DistributedLog provides the following key features:
- High Performance
- Durable and Consistent
- Efficient Fan-in and Fan-out
DistributedLog is an open source tool with 2.25K GitHub stars and 283 GitHub forks. Here's a link to DistributedLog's open source repository on GitHub.
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!