feat: In-Memory TTL Cache Service for Horizon Responses (#196)#240
Merged
Sulex45 merged 2 commits intoJun 8, 2026
Merged
Conversation
…ab-devtools#196) Add a node-cache based service at src/services/cache.js and apply it to network-status, fee-estimate, and asset endpoints with configurable TTLs. Includes X-Cache headers, ?fresh=true bypass, and comprehensive tests.
Contributor
|
Resolve Conflicts |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Build a centralised in-memory cache service that all routes can use to cache Horizon responses with configurable TTLs.
Changes:
CacheServiceinsrc/services/cache.jsusingnode-cache/network-status(5s TTL)/fee-estimate(5s TTL)/asset/:code/:issuer(30s TTL)X-Cache: HIT/MISSheaders?fresh=trueCloses #196