You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A fully managed message queue service offered by AWS. It provides a reliable, scalable, and cost-effective way to decouple and coordinate distributed software systems and microservices.
3
+
4
+
### Libraries for Amazon SQS (Simple Queue Service)
5
+
- GO: [sqs](https://github.com/core-go/sqs), to wrap and simplify [aws-sdk-go/service/sqs](https://github.com/aws/aws-sdk-go/tree/main/service/sqs). Example is at [go-amazon-sqs-sample](https://github.com/project-samples/go-amazon-sqs-sample)
6
+
7
+
#### A common flow to consume a message from a message queue
8
+

9
+
- The libraries to implement this flow are:
10
+
-[mq](https://github.com/core-go/mq) for GOLANG. Example is at [go-amazon-sqs-sample](https://github.com/project-samples/go-amazon-sqs-sample)
11
+
12
+
### Use Cases of Amazon SQS (Simple Queue Service)
- <b>Management</b>: Pub/Sub and SQS are managed services, while Kafka is typically self-managed or via managed services like Confluent.
61
+
- <b>Use Case Focus</b>: Pub/Sub and Kafka are ideal for real-time processing, whereas SQS is great for decoupling microservices and handling asynchronous tasks.
62
+
- <b>Delivery Models</b>: Pub/Sub supports push and pull, SQS supports pull with long polling, and Kafka primarily uses pull with consumer groups.
63
+
- <b>Scalability</b>: All three are highly scalable, but Kafka offers the most control over performance tuning.
64
+
- <b>Integration</b>: Pub/Sub integrates well with Google Cloud, SQS with AWS, and Kafka has a broad integration ecosystem.
2
65
3
66
## Installation
4
67
5
-
Please make sure to initialize a Go module before installing common-go/sqs:
68
+
Please make sure to initialize a Go module before installing core-go/sqs:
0 commit comments