feat: implement Redis-based caching layer for service discovery (#316)#355
Closed
Abhushan187 wants to merge 3 commits into
Closed
feat: implement Redis-based caching layer for service discovery (#316)#355Abhushan187 wants to merge 3 commits into
Abhushan187 wants to merge 3 commits into
Conversation
|
@Abhushan187 is attempting to deploy a commit to the souma9830's projects Team on Vercel. A member of the Team first needs to authorize it. |
Owner
|
Resolve conflict and tell me under which open source program |
Contributor
Author
merge conflict resolved and im nsoc'26 contributor ,is this project part of gssoc'26 as well btw ? |
Owner
|
still have merge conflict |
Contributor
Author
checkout now and please merge it before 15th june for nsoc evaluation |
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
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.
Closes #316
Changes by file
server/package.jsonioredis^5.6.1 dependency.server/config/redis.jsgetOrSetCachehelper (cache-aside with TTL),deleteCachePatternfor wildcard invalidation, graceful disconnect.server/controllers/issueController.jsgetNearbyIssueswithgetOrSetCache(5-min TTL). Added cache invalidation increateIssueandupdateIssueStatusfor the affected category.server/server.jsdisconnectRedis; added SIGTERM/SIGINT graceful shutdown handler..env.example/server/.env.exampleREDIS_URLdocumentation.Technical Notes
ioredischosen overnode-redisfor built-in cluster support, pipelining, and robust reconnection.nearby:{lat}:{lng}:{category}:{radius}:{zoom}— lat/lng rounded to 4 decimals (~11m precision) to balance granularity vs cache hit rate.getOrSetCachefalls back to DB query on any Redis error — no cache outage takes down the API.deleteCachePatternusesscanStream+pipelineto avoidKEYSblocking on large datasets..catchon promise) to avoid blocking the response.