DOC-6565 cache aside use case#3291
Conversation
❌ Jit Scanner failed - Our team is investigatingJit Scanner failed - Our team has been notified and is working to resolve the issue. Please contact support if you have any questions. 💡 Need to bypass this check? Comment |
❌ Jit Scanner failed - Our team is investigatingJit Scanner failed - Our team has been notified and is working to resolve the issue. Please contact support if you have any questions. 💡 Need to bypass this check? Comment |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 585deba. Configure here.
❌ Jit Scanner failed - Our team is investigatingJit Scanner failed - Our team has been notified and is working to resolve the issue. Please contact support if you have any questions. 💡 Need to bypass this check? Comment |

This is still in development - just making a PR to get an early review from the bugbot while the rest of the stuff is being generated.
Note
Low Risk
Low risk because this PR only adds new documentation pages and sample/demo code under
content/, with no changes to production application logic.Overview
Introduces a new Redis cache-aside use-case section (
content/develop/use-cases/cache-aside) describing when/why to use the pattern and linking out to language-specific guides.Adds full example implementations for Go (
go-redis), .NET (StackExchange.Redis), and Java (Jedis + Lettuce), each including a small local demo server/UI plus a cache helper that supports TTL-bounded reads, invalidate-on-write, optional in-place field updates, basic hit/miss stats, and Lua-based single-flight locking to mitigate cache stampedes.Reviewed by Cursor Bugbot for commit 313c95b. Bugbot is set up for automated code reviews on this repo. Configure here.