Compress the response content if it's large enough
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
The response we sent is sometimes fairly large. Sometimes it's greater than 300KiB. We could save quite a bit of bandwidth by compressing it.
- Recognize `accept-encoding` HTTP header and compress the response on the fly.
- Support gzip, deflate and brotli
- Cache the compressed result if possible.
This will require the work on the Armeria side first.
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 investigating the required Armeria-side work, since the issue identifies it as a prerequisite. Then trace how Central Dogma sends HTTP responses and determine where Accept-Encoding handling, gzip/deflate/brotli support, and compressed-result caching belong. Done means responses larger than 300 KiB are compressed according to the header and the compressed result is cached when possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100