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
Is your feature request related to a problem? Please describe.
Currently, the project supports a variety of message brokers, including RabbitMQ, Kafka, and GCP Pub/Sub. However, many users rely heavily on AWS services and would benefit from the ability to utilize AWS SQS as an additional message broker option.
Describe the solution you'd like
I propose adding support for AWS SQS as a new message broker option. This would involve implementing a new SQS producer and consumer, allowing users to seamlessly integrate their existing AWS infrastructure with the project.
Describe alternatives you've considered
While the existing supported brokers are excellent options, AWS SQS offers unique advantages such as:
Simplified Message Queues: AWS SQS provides a fully managed message queuing service, eliminating the need for complex infrastructure setup and management.
Robustness and Scalability: AWS SQS is highly scalable and durable, ensuring reliable message delivery even under heavy load.
Cost-Effective: AWS SQS offers a flexible # model, making it a cost-effective solution for various use cases.
Additional context
I love this project and I'm eager to contribute by developing the necessary code for SQS integration. I'm confident in my ability to deliver a high-quality implementation that aligns with the project's coding standards and best practices.
I'm available to discuss this feature request further and answer any questions you may have.
The text was updated successfully, but these errors were encountered:
I would definitely merge a contribution to support SQS and SNS. I only built those that I use myself, apart from Kafka (and that one isn't complete either).
Is your feature request related to a problem? Please describe.
Currently, the project supports a variety of message brokers, including RabbitMQ, Kafka, and GCP Pub/Sub. However, many users rely heavily on AWS services and would benefit from the ability to utilize AWS SQS as an additional message broker option.
Describe the solution you'd like
I propose adding support for AWS SQS as a new message broker option. This would involve implementing a new SQS producer and consumer, allowing users to seamlessly integrate their existing AWS infrastructure with the project.
Describe alternatives you've considered
While the existing supported brokers are excellent options, AWS SQS offers unique advantages such as:
Simplified Message Queues: AWS SQS provides a fully managed message queuing service, eliminating the need for complex infrastructure setup and management.
Robustness and Scalability: AWS SQS is highly scalable and durable, ensuring reliable message delivery even under heavy load.
Cost-Effective: AWS SQS offers a flexible # model, making it a cost-effective solution for various use cases.
Additional context
I love this project and I'm eager to contribute by developing the necessary code for SQS integration. I'm confident in my ability to deliver a high-quality implementation that aligns with the project's coding standards and best practices.
I'm available to discuss this feature request further and answer any questions you may have.
The text was updated successfully, but these errors were encountered: