cloudamqp / cloudamqp/amqproxy
Design capacity planning for amqp-proxy
Open
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 408
- Forks
- 50
- Avg merge
- 18h 30m
- Merged PRs (30d)
- 3
Description
It would be interesting to have a capacity planning to understand the limits or how to properly size instances to handle certain workloads.
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 reviewing amqproxy's connection and channel pooling behavior, then define representative AMQP workloads and the instance limits to measure. The issue needs agreed sizing questions, benchmark scenarios, and success criteria before implementation can begin; no files or tests are identified in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal, rabbitmq
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100