Önbellek Arka Uçları ve Redis

A cache stores expensive results so the next request can skip the slow work and reply almost instantly. ⚡

Django talks to a cache through a backend, a pluggable adapter that decides where your cached data is physically stored.

You configure caching in the CACHES dict in settings.py, always with a key named default that Django reads first.

The default LocMemCache keeps data in your process memory. It is fine for development but is not shared across servers.

For real apps, point the backend at Redis, a fast in-memory store that many web servers can share at once.

Set BACKEND to RedisCache and give it a LOCATION pointing at your Redis server URL.

Import the shared cache object from django.core.cache to read and write values from anywhere in your code.

Use set to store a value under a key, then get to read it back later in another request.

The third argument to set is a timeout in seconds. After it passes, the key expires and get returns None.

A missing key is a cache miss. Pass a default to get so your code has a safe value to fall back on.

Beyond Redis, Django ships database and file-based backends, handy when you cannot run a separate memory server.

You met the cache backend: configure CACHES, use LocMem in dev and Redis in production, then set and get values with a timeout. 🎉