Add scheduled cache warming job

[utahkanz-ops]

Summary

• Added a scheduled backend cache warming job for frequently accessed market/event data.

Issue

• Closes [Backend] — Implement Cache Warming Job #756

Changes

• Added CacheWarmingService scheduled to run every 10 minutes.
• Warms active public events, trending events, platform/category statistics, and popular event details.
• Added configurable warming strategy through env-backed ConfigService values.
• Added stable cache warming keys and logging for warming success/failure.
• Registered CacheWarmingModule in the backend app module.
• Added unit tests for successful warming, partial failure handling, and disabled warming.

Validation

• npm ci --ignore-scripts --no-audit --no-fund passed in backend.
• npx prettier --write src/cache/**/*.ts src/app.module.ts passed.
• npx jest --runInBand src/cache/warming.service.spec.ts passed: 3 tests.
• npm run build passed.
• git diff --check passed.

Notes

• Commit author verified as utahkanz-ops <272119084+utahkanz-ops@users.noreply.github.com>.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
insight-arena-4rll	Ready	Preview, Comment	May 28, 2026 6:16pm

[drips-wave]

@utahkanz-ops Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits