The document discusses cache service design using Redis. It proposes using HTTP cache control directives like max-age, private and no-store to control caching of responses. A flow diagram shows the first request fetching data while a second unchanged request gets data from cache, improving performance. An example API GET request to /dbee/v1/notifications endpoint is also included.

1. CacheServiceDesign
withRedis
Rich.Lee
2018/12/15

3. https://redis.io/topics/persistence

9. RFC 2616

10. Directives Explanation
max-age=86400 Response can be cached by browser and any intermediary caches (that is,
it's "public") for up to 1 day (60 seconds x 60 minutes x 24 hours).
private, max-age=600 Response can be cached by the client’s browser only for up to 10 minutes (60
seconds x 10 minutes).
no-store Response is not allowed to be cached and must be fetched in full on every
request.

12. 1. First request for data 2.The second request for data,
but the content has not changed

14. Flow diagram

17. http://10.120.138.215:8196/dbee/v1/auth

23. HTTP GET /dbee/v1/notifications