HTTP caching is a powerful technique for optimizing web performance and reducing server load. In this comprehensive guide, we’ll explore the fundamentals of HTTP caching, its benefits, implementation strategies, and best practices to help you harness its full potential.
In this article, we explore the concepts of cache avalanche, cache breakdown, and cache penetration, common issues that can affect the performance of caching systems. We discuss the causes of these problems, their impact on system performance, and strategies to mitigate their effects.
Rails page caching and nginx make a natural pair: nginx serves the HTML files Rails writes to public/ straight from disk, and its proxy cache (stored on disk, indexed in shared memory) holds every other public response. In this guide, we’ll configure both, with a safe cache key, session-cookie bypass, cache locking and stale serving.
Serving whole pages from a shared cache breaks Rails forms, because every visitor receives the CSRF token that was rendered for someone else. In this post, we’ll cache public pages with Rack::Cache backed by Redis and look at two ways to keep CSRF tokens working: fetching a fresh token with JavaScript from a small uncached endpoint, and a Rack middleware that injects one on the server.
Varnish can cache whole Rails pages in memory and serve them without touching the application, but only if Rails tells it which pages are safe to share. In this article, we’ll let Rails mark public pages with Cache-Control, configure Varnish to honour those headers without leaking one user’s page to another, and add PURGE/BAN invalidation.
Page caching is a technique used to improve the performance of web applications by storing the entire HTML output of a page and serving it directly from the cache for subsequent requests. This eliminates the need to generate the page dynamically on each request, reducing server load and improving response times. In this article, we’ll explore the concept of page caching, the HTTP caching basics it relies on, and the main places a full page can be cached, plus related techniques that cache smaller pieces.
Redis is an in-memory data structure store known for its speed and flexibility. It serves as a high-performance database, cache, and message broker, offering data structures such as strings, hashes, lists, sets, and sorted sets. This article covers how Rails applications use Redis for caching, sessions, background jobs and counters, how to set up Rails’ built-in Redis cache store, and when Rails 8’s database-backed defaults make Redis optional.