|
You are here |
blog.bigdinosaur.org | ||
| | | | |
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. | |
| | | | |
httptoolkit.com
|
|
| | | | | If you run any large public-facing website or web application on the modern web, caching your static content in a CDN or other caching service is super... | |
| | | | |
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. | |
| | | | |
inphotos.org
|
|
| | | Afraid of heights? Don't go up in a hot air balloon! | ||