Redis Fundamentals
Redis is an in-memory data store that keeps values under keys and provides data structures such as strings, hashes, sets, and streams. You use it when fast access to transient or actively managed data fits the workload, with explicit choices for memory, persistence, and availability.
itDatabases and data storage | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Redis Fundamentals
Redis is a data structure server. Your application addresses a value with a key, then uses commands designed for that value's data type. That model makes Redis useful for more than a cache: it can hold counters, sessions, queues, rankings, streams, and short-lived coordination data.
The central question is not "Can Redis store this?" It is "What data structure and failure behavior does this workload need?" A string with a time to live fits a cached response. A hash fits fields of one entity. A sorted set fits members ranked by a score. A stream fits an append-only event log.
How Redis fits
Redis receives commands from a client and stores the resulting dataset in memory. A key names one value, and the value has a data type. Commands operate on that type. A type mismatch is a design signal: choose the structure that expresses the operation you need instead of forcing everything into serialized blobs.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://redis.io/docs/latest/develop/data-types/
Supports
- Redis is a data structure server with native data types
- Strings, hashes, lists, sets, sorted sets, and streams support different workloads
- Streams act as append-only logs and sorted sets order unique members by score
- https://redis.io/docs/latest/develop/clients/
Supports
- Applications connect to Redis through client libraries
- Redis documents supported client libraries for common languages
- redis-cli and Redis Insight can interact with a Redis server
- https://redis.io/docs/latest/operate/oss_and_stack/management/persistence/
Supports
- Redis persistence uses RDB snapshots and append-only files
- Persistence settings involve recovery and data-loss tradeoffs
- https://redis.io/docs/latest/operate/oss_and_stack/management/replication/
Supports
- Redis replication is asynchronous by default
- WAIT requests replica acknowledgements but does not provide strong consistency
- Replication supports read scaling and high availability with operational limits
- https://redis.io/docs/latest/operate/oss_and_stack/management/scaling/
Supports
- Redis Cluster partitions keys across multiple nodes
- Cluster design affects key placement and client behavior
- https://redis.io/docs/latest/develop/pubsub/
Supports
- Redis pub/sub delivers messages to current subscribers
- Disconnected pub/sub subscribers do not receive prior messages
- https://redis.io/docs/latest/operate/oss_and_stack/management/eviction/
Supports
- Redis maxmemory and eviction policies control behavior under memory pressure
- Keys can be evicted according to the selected policy
