O que são os Redis Streams?
Entenda a arquitetura e os benefícios dos Redis Streams como uma fila de mensagens persistente e avançada.
O que são os Redis Streams? é uma aula grátis de Redis Caching & Messaging (Pub/Sub, Streams) no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Redis Caching & Messaging (Pub/Sub, Streams), e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Redis Caching & Messaging (Pub/Sub, Streams) inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
What are Redis Streams?
Welcome! In this lesson, we'll dive into Redis Streams, a powerful data structure for managing real-time event data.
Think of a stream as an append-only log of messages, similar to a traditional message queue or a Kafka topic, but built right into Redis.
Streams are ideal for building event-driven architectures, processing sensor data, or tracking user activity.
Streams vs. Pub/Sub
Redis already has Pub/Sub, so why Streams?
- Persistence: Stream messages are stored and not lost if consumers are offline. Pub/Sub messages are fire-and-forget.
- Consumer Groups: Streams support consumer groups for cooperative message processing, allowing multiple applications to read the same stream without duplicating work.
- Message History: You can read messages from any point in the stream's history.
Streams offer durability and advanced consumption patterns that Pub/Sub doesn't.
Stream Architecture: Entries & IDs
A Redis Stream is an ordered sequence of entries. Each entry is composed of:
- A unique Stream ID: This is a timestamp-based ID (e.g.,
1678886400000-0) that ensures messages are strictly ordered. - One or more field-value pairs: These are the actual data for the message, similar to a small Redis Hash.
Think of it as a log where each line has a unique timestamp and some key-value data.
Adding Entries with XADD
Producers add new entries to a stream using the XADD command. Redis automatically generates a unique ID for each new entry, or you can provide one.
The * wildcard tells Redis to generate a new, unique ID for the entry.
Try running this example:
public class Main {
public static void main(String[] args) {
System.out.println("Simulating Redis XADD command:");
String streamName = "sensor_data";
// XADD sensor_data * temp 25 hum 60
System.out.println("redisClient.xadd(");
System.out.println(" \"" + streamName + "\", \"*\",");
System.out.println(" \"temp\", \"25\", \"hum\", \"60\"");
System.out.println(");");
System.out.println("\nOutput (example ID): 1678886400000-0");
}
}Understanding Stream IDs
Stream IDs have two parts: <milliseconds-timestamp>-<sequence-number>.
- The timestamp is the time the entry was added (in Unix milliseconds).
- The sequence number is incremented if multiple entries are added within the same millisecond.
This structure guarantees that IDs are always increasing, providing a natural order for messages. You can use 0-0 to refer to the very beginning of a stream.
Reading from a Stream with XREAD
Consumers use the XREAD command to retrieve entries from one or more streams. You specify the stream name and the ID from which to start reading.
XREAD allows you to fetch a batch of messages, making it efficient for consumers.
Try running this example:
public class Main {
public static void main(String[] args) {
System.out.println("Simulating Redis XREAD command:");
String streamName = "sensor_data";
String startId = "0-0"; // Read from the beginning
// XREAD STREAMS sensor_data 0-0
System.out.println("List<Map<String, String>> entries =");
System.out.println(" redisClient.xread("STREAMS",");
System.out.println(" \"" + streamName + "\", \"" + startId + "\"");
System.out.println(");");
System.out.println("\nExample Output:");
System.out.println("ID: 1678886400000-0, {temp=25, hum=60}");
System.out.println("ID: 1678886400001-0, {temp=26, hum=61}");
}
}Blocking Reads for Real-time
To read new messages as they arrive, you can use the BLOCK option with XREAD. This makes the command wait for new data if no new entries are available.
You can also specify a timeout for the blocking operation. This is crucial for building real-time applications that react instantly to events.
Example: XREAD BLOCK 0 STREAMS mystream $ ($ means 'last ID in stream').
Stream Persistence & History
Unlike Pub/Sub, Redis Streams are persistent. Messages added to a stream remain there until explicitly removed or trimmed.
This allows new consumers to read the entire history of events from the beginning, or catch up from a specific point if they were temporarily offline.
This persistence is a key feature for reliable event logging and replay capabilities.
Ordered & Immutable Entries
Redis Streams guarantee that entries are always added in the order they are received and assigned strictly incrementing IDs.
Once an entry is added to a stream, it cannot be modified. This immutability is fundamental for maintaining an accurate, auditable log of events.
These properties make Streams excellent for event sourcing and ensuring data consistency.
Check Your Understanding
Which of the following are key benefits or characteristics of Redis Streams?
Recap: What are Redis Streams?
In this lesson, we learned that Redis Streams are a powerful, persistent, append-only log data structure.
- They offer persistence, ordered delivery, and support for consumer groups, differentiating them from Pub/Sub.
- We explored how to add entries with
XADDand read them withXREAD. - Streams are ideal for event sourcing, real-time data processing, and building reliable message queues.
Next, we'll dive deeper into Stream commands and features!
Aprenda Redis Caching & Messaging (Pub/Sub, Streams) com um tutor de IA — grátis
Escreva e execute código real no seu navegador, obtenha ajuda instantânea de um tutor de IA 24/7 e continue de onde parou na web ou no app.
- Cursos
- 12
- Aulas
- 48
Perguntas Frequentes
A aula “O que são os Redis Streams?” é grátis?
Sim — o texto completo de “O que são os Redis Streams?” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Redis Caching & Messaging (Pub/Sub, Streams), atualize para CoddyKit PRO. O curso de Redis Caching & Messaging (Pub/Sub, Streams) inclui 4 aulas no total.
O que vou aprender em “O que são os Redis Streams?”?
Entenda a arquitetura e os benefícios dos Redis Streams como uma fila de mensagens persistente e avançada. Você pratica Redis Caching & Messaging (Pub/Sub, Streams) com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Redis Caching & Messaging (Pub/Sub, Streams)?
Nenhuma experiência prévia é necessária. Redis Caching & Messaging (Pub/Sub, Streams) no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.
Quanto tempo leva a aula “O que são os Redis Streams?”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Redis Caching & Messaging (Pub/Sub, Streams)?
Sim. Cada aula de Redis Caching & Messaging (Pub/Sub, Streams) inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- O que são os Redis Streams?
- Estruturas de dados e comandos de fluxo
- Persistência de mensagens em fluxos
- Limitando e aparando fluxos