[Core/Perf] Distributed caching system for recently scanned safe URLs

[Diwakar-odds]

Introduce a caching layer (Memcached or Redis) to store the threat analysis results of commonly scanned URLs. This will save significant processing time and external API quotas.

Please assign this to me under ECSoC26.

[Diwakar-odds]

Hi @Mrinalray, I would love to work on this issue under ECSoC '26.

As this is a core backend feature, here is my technical proposal for implementing the distributed caching system:

Step-by-Step Implementation Plan

1. Dependency Addition: Install the
   edis package for the caching layer.
2. Redis Initialization: Configure server.js to connect to a Redis client using a REDIS_URL environment variable. If Redis is unavailable, it will fail gracefully and bypass the cache.
3. Cache Retrieval: In the /check route, query the Redis cache using the userUrl as the key before making a request to the Google Safe Browsing API.
4. Cache Miss & Storage: On a cache miss, fetch the data from the Google API, then store the exact result in Redis with a 24-hour TTL (Time-To-Live) to ensure the threat status remains updated.

Files to be Modified

• package.json / package-lock.json: Add
  edis dependency.
• server.js: Integrate the Redis client and update the /check endpoint.
• README.md: Document the new REDIS_URL environment variable.

I am ready to start on this L3 feature immediately once assigned. Please let me know if this approach aligns with your vision!

[Mrinalray]

@Diwakar-odds assigned