CloudAMQP vs pg-amqp-bridge: What are the differences?
Developers describe CloudAMQP as "RabbitMQ as a Service". Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms. On the other hand, pg-amqp-bridge is detailed as "Send Messages from PostgreSQL to RabbitMQ". This tool enables a decoupled architecture, think sending emails when a user signs up. Instead of having explicit code in your signup function that does the work (and slows down your response), you just have to worry about inserting the row into the database.
CloudAMQP and pg-amqp-bridge can be primarily classified as "Message Queue" tools.
pg-amqp-bridge is an open source tool with 251 GitHub stars and 14 GitHub forks. Here's a link to pg-amqp-bridge'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!