[Perf] Replace hardcoded cache TTLs with a dynamic tier-based strategy

[nanaf6203-bit]

Problem Statement

src/lib/cacheManager.ts and src/lib/redisCache.ts hardcode TTLs:

PROPERTY_LISTINGS: 5 * 60,
PROPERTY_DETAILS: 1 * 60,
SEARCH_RESULTS: 5 * 60,
AUTOCOMPLETE: 10 * 60

There is no environment-aware tuning. In dev/staging, indexes shift frequently; in production, longer TTLs are safe but invalidate stale snapshots faster than necessary. There's no per-tenant TTL override.

Expected Outcome

• TTLs are computed dynamically based on NODE_ENV, feature flag, or per-property hotness
• A function ttlFor(contentType, hotnessTier) returns the right seconds
• A future per-region override is one place to plug in

Acceptance Criteria

• New src/lib/cacheTtl.ts module with documented tier mappings
• Old hardcoded constants removed from callers
• Tests verify TTL under each tier

Implementation Notes

Introduce hotness = (recentAccesses) => high | medium | low and look up from a tier table. Default tier: medium.

Files Likely Affected

• src/lib/redisCache.ts
• src/lib/cacheManager.ts
• Possibly: src/lib/propertyService.ts (consumers)

Difficulty / Effort

• Difficulty: Easy
• Effort: T-Shirt S

Labels

enhancement, priority:medium, area:performance, area:caching

[Samuelaladesiun3334]

@Samuelaladesiun3334 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please I would love to work on this project

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Samuelaladesiun3334 to this issue.

[mirastan]

@mirastan has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i'd really like to contribute by tackling this issue. kindly assign me to tackle this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mirastan to this issue.

[boss572]

@boss572 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer please I will like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @boss572 to this issue.

[drips-wave]

Congratulations, @mirastan! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @mirastan: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊