otto-de / otto-de/api-guidelines
[define] evaluate possibilities for SNS/SQS CloudEvents binding
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 50
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
(i) This issue has been manually transferred from a former internal repository, as a private repository issue cannot be transferred to a public repository.
Context
SNS/SQS is a popular async protocol within OTTO.
With this ticket, it should be evaluated if an SNS/SQS protocol binding for CloudEvents can be specified.
Reference
- Closed (not implemented) issue on CloudEvents repo: https://github.com/cloudevents/spec/issues/435
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked CloudEvents issue and the SNS/SQS context in this issue. Evaluate whether an SNS/SQS protocol binding can be specified, and document the resulting feasibility decision or specification direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100