al eager caching server.

Powered by FastAPI.

There is a dockerfile, dockercompose and k8s yamls.

Make sure you have a running redis deployment, set to notify keyspace events:

redis-cli config set notify-keyspace-events Ex

Say you have some data that you need to serve to your users. You decide to use a cache, but then you realise you need also to invalidate the cache after some time. Another consideration you tak into account is serving your users with fresh information every time they want to access the data, using the cache.

Introducing eager-cache: In its base, it's a FastAPI server that uses supplied fetchers in order to serve users with information they need. It's actually a key-value store, storing cache in redis for each request (path+query) the value retrieved from the appropriate fetcher.

The magic is in the caching mechanism. It uses redis in order to store the cached responses, and sets ttl for every cache record using a shadow key for each record.

There is a microservice that subscribes to keyspace events from the redis deployment and refetches the expired value using the fetcher.

In addition to storing the data, DataItem does two important things:

First, it stores the time the data itself was fetched (this is last_retrieved).

Second, it stores the time the data itself was changed (this is last_modified).

This way, you can always know when was the data fetched, but also when was it changed (the comparison is done using deepdiff)