SSWConsulting / SSWConsulting/SSW.Website
💸 Investigate - Caching options
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
@wicksipedia
Recently, our website experienced a surge in requests from CodeAuditor, resulting in slower response times and occasional unresponsiveness. To address this issue and prevent similar occurrences in the future, we need to investigate caching options. While Front Door caching is a potential solution, purging cached content can be time-consuming and challenging to validate.
- Explore caching options.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by documenting the current request and deployment path, then compare caching options with attention to cache purging and validation. Done means a caching approach is selected with a documented plan for purging and verifying cached content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, nextjs
- Domain
- cloud, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100