/explore
|
You are here 
|
qnoid.com | ||
| | | | |
techblog.thescore.com
|
|
| | | | | Cache-Control directives are pretty straightforward to understand. They're easy to use as well if you assume that all the caches between your end user and application correctly implement the spec. Unfortunately, as with any spec, you can't make that assumption. | |
| | | | |
www.integralist.co.uk
|
|
| | | | | Introduction Caching is hard. Let's try and understand it a little better. Note: some sections are purposefully brief. I'm not aiming to be a specification document. Caching at multiple layers Caching can occur at both a 'client' level and a 'cache proxy' level. Consider the following request flow architecture diagram... In the above diagram, the "CDN" is a 'caching proxy' and so caching can (and of course does) happen there. | |
| | | | |
truemped.github.io
|
|
| | | | | My usual web application stack for the past years was based on a nginx as reverse proxy in front of a number of Python processes. Static resources were served by nginx. Each Python process was stateless, state was stored in some kind of database. If the processes needed some shared ephemeral state like counters a local redis instance solved that. A battle tested common ground for Python based web applications. | |
| | | | |
paul.kinlan.me
|
|
| | | Paul is a Developer Advocate for Chrome and the Open Web at Google and loves to help make web development easier. | ||
