Skip to content

feat(backend): add Redis distributed cache for plan metadata#643

Open
od-hunter wants to merge 1 commit into
Smartdevs17:mainfrom
od-hunter:feature/redis-plan-metadata-cache
Open

feat(backend): add Redis distributed cache for plan metadata#643
od-hunter wants to merge 1 commit into
Smartdevs17:mainfrom
od-hunter:feature/redis-plan-metadata-cache

Conversation

@od-hunter

Copy link
Copy Markdown
Contributor

Closes #592

Introduce PlanCacheService with write-through caching, single-flight
protection, Prometheus metrics, and cache warming on deploy. Wire into
GraphQL loaders, REST plan endpoints, and a new backend server entry
point with Redis/Postgres docker-compose support.
@drips-wave

drips-wave Bot commented Jun 24, 2026

Copy link
Copy Markdown

@od-hunter 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

@gitguardian

gitguardian Bot commented Jun 24, 2026

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Generic Password fbb20e6 backend/config/tests/redis.test.ts View secret
15742864 Triggered Generic Password fbb20e6 docker-compose.yml View secret
15762030 Triggered Generic Password fbb20e6 docker-compose.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Redis-based distributed caching for subscription plan metadata

1 participant