Redis Cache design
0 likes•90 views
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 of 23
Download to read offline
More Related Content
PDF
Don't Build "Death Star" Security - O'Reilly Software Architecture Conference...David Timothy StraussDon't Build "Death Star" Security - O'Reilly Software Architecture Conference...David Timothy Strauss
More from Rich Lee (7)
Ad
Recently uploaded (20)
PDF
Balancing Resource Capacity and Workloads with OnePlan – Avoid Overloading Te...OnePlan SolutionsPDF
Teaching Reproducibility and Embracing Variability: From Floating-Point Exper...University of Rennes, INSA Rennes, Inria/IRISA, CNRSTeaching Reproducibility and Embracing Variability: From Floating-Point Exper...University of Rennes, INSA Rennes, Inria/IRISA, CNRS
Ad
Redis Cache design
- 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