Amazon SQS vs pg-amqp-bridge: What are the differences?

### Introduction
In this markdown, we will discuss the key differences between Amazon SQS and pg-amqp-bridge.

1. **Messaging Protocol**: Amazon SQS uses a proprietary messaging protocol specific to its service, while pg-amqp-bridge utilizes the AMQP protocol, which is an open standard for messaging.
2. **Service Integration**: Amazon SQS is tightly integrated with other AWS services, allowing seamless communication within the AWS ecosystem, whereas pg-amqp-bridge provides a bridge between PostgreSQL and AMQP, offering a specific use case for integrating these two systems.
3. **Managed Service vs. Self-Hosted**: Amazon SQS is a fully managed service provided by AWS, eliminating the need for users to manage infrastructure or scaling, whereas pg-amqp-bridge requires users to self-host and manage the deployment and maintenance of the service.
4. **Scalability**: Amazon SQS is designed to handle high throughput and scale automatically based on the workload, offering a highly scalable solution out of the box, whereas pg-amqp-bridge may require manual intervention for scaling based on the workload and infrastructure capacity.
5. **Message Visibility**: Amazon SQS provides fine-grained control over message visibility timeout and delivery guarantees, allowing users to configure message retention and processing, while pg-amqp-bridge may have limited visibility control depending on the configuration of the PostgreSQL database.

### Summary
In summary, Amazon SQS and pg-amqp-bridge differ in their messaging protocols, service integration, management model, scalability, and message visibility controls.