go-kit/kit

Feature request: AWS SQS transport

Open

#858 opened on Apr 9, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (27,422 stars) (2,446 forks)batch import
enhancementhelp wanted

Description

This is different from pubsub #295 because it is specific to message handling from AWS SQS, not a generic pubsub solution. I am envisioning something modeled very similarly to the AMQP transport. I was going to try to implement this; would there be interest from the team if we proposed it as a PR?

Contributor guide

Tech stack
go
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingAWS SQS API knowledgefamiliarity with go kit transport patterns
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Review the existing AMQP transport implementation in go kit/kit to understand the pattern. Check the AWS SQS Go SDK documentation. Consider asking the maintainers for feedback on the proposed design before proceeding. The issue has minimal discussion, so open a new comment to clarify requirements.