/explore
|
You are here 
|
qnoid.com | ||
| | | | |
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. | |
| | | | |
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. | |
| | | | |
www.mnot.net
|
|
| | | | | A long, long time ago, I wrote some tests using XmlHttpRequest to figure out how well browser caches behaved, and wrote up the results. | |
| | | | |
gehrcke.de
|
|
| | | Has Google become more conservative with indexing content of personal websites? I think we might see less and less low-traffic quality contents in Google search results. I have carefully done basic... | ||
