Einführung in Redis

Redis (Remote Dictionary Server) is a blazing-fast, in-memory key-value store. Developers reach for it for caching, sessions, and real-time analytics.

Redis is in-memory: it keeps data in RAM, making reads and writes far faster than disk-based databases. It can still persist to disk when you need durability.

At its core Redis is a key-value store — look up a value by its unique key, like a dictionary. Values can be strings, lists, hashes, or sets.

Redis is fast for three reasons: it's in-memory, written in optimized C, and single-threaded — which avoids locks on data operations entirely.

The classic use case is caching: store hot data in Redis so repeat reads come back instantly, sparing your slow database and speeding up the app.

Redis is great for user session data. Any server can read the shared session, so it scales web apps where requests hit different machines.

Speed plus rich data structures make Redis ideal for real-time features: leaderboards, live analytics, and Pub/Sub messaging between services.

Redis uses a client-server model: the server runs as a process waiting for connections, and your clients send commands and get responses back.

Two ways to talk to Redis: the redis-cli for manual testing and admin, or client libraries (Python, Java, Node) for talking to it from your code.

Based on what you've learned, which of the following are key characteristics or common use cases of Redis?

Recap: Redis is an in-memory key-value store, fast by design, used for caching, sessions, and real-time features over a simple client-server architecture.