feat: Edge Cache Service with Cloudflare Cache API support #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces a high-performance Edge Cache Service leveraging Cloudflare's Cache API for sub-10ms access times. The implementation is based on production-tested patterns from the Kogotochki bot project.
Key Features:
Implementation Details:
Changes
New Files:
src/core/interfaces/cache.ts
- Cache service interfacessrc/core/services/cache/edge-cache-service.ts
- Main Edge Cache Service implementationsrc/middleware/edge-cache.ts
- Hono middleware for automatic cachingdocs/EDGE_CACHE.md
- Comprehensive documentationexamples/edge-cache-example.ts
- Working example with all featuresTest Coverage:
src/core/services/cache/__tests__/edge-cache-service.test.ts
- Service unit testssrc/middleware/__tests__/edge-cache.test.ts
- Middleware integration testsUsage Example
Performance Benefits
Production Metrics
From Kogotochki bot deployment:
Testing
All tests pass:
Documentation
See
docs/EDGE_CACHE.md
for:Breaking Changes
None. This is a new feature that doesn't affect existing functionality.
Checklist