Add response caching with TTL for `GET /api/apis` marketplace listings

[greatest0fallt1me]

Description

Once GET /api/apis reads from the database it will be a hot, mostly-read endpoint for the marketplace. This backend task adds a short-TTL cache layer with explicit invalidation on API create/update so listing reads stay fast without serving stale catalogs.

Requirements and Context

• Add a cache abstraction with TTL keyed by listing query params.
• Invalidate on writes through src/repositories/apiRepository.ts.
• Emit cache hit/miss counters via src/metrics.ts.
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b feature/apis-listing-cache

2. Implement changes
   • New cache helper under src/lib/
   • src/routes/apis.ts — cache lookups
   • src/metrics.ts — add hit/miss counters
3. Test and commit
   • npm test -- src/__tests__/metricsLatency.test.ts
   • Cover edge cases
   • Include test output and notes in the PR

Example commit message

feat: cache GET /api/apis listings with TTL invalidation

Acceptance Criteria

• Repeated listing reads within TTL hit the cache
• API create/update invalidates affected cache keys
• Cache hit/miss metrics are exported

Guidelines

• Minimum 90% test coverage with Jest
• Clear documentation and inline comments
• Timeframe: 96 hours

[elijah4196]

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

This issue interests me because it combines database structure improvements with testing, both of which are important in building reliable applications.

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

[drips-wave]

Congratulations, @elijah4196! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @elijah4196: 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 🌊