What is pg-amqp-bridge?
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.
pg-amqp-bridge is a tool in the Message Queue category of a tech stack.
pg-amqp-bridge is an open source tool with 276 GitHub stars and 18 GitHub forks. Here’s a link to pg-amqp-bridge's open source repository on GitHub
Who uses pg-amqp-bridge?
Why developers like pg-amqp-bridge?
Here’s a list of reasons why companies and developers use pg-amqp-bridge
Be the first to leave a pro
pg-amqp-bridge Alternatives & Comparisons
What are some alternatives to pg-amqp-bridge?
See all alternatives
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.
Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.