Workshop Description:
Redis, the in-memory multi model database, is popular for many use cases, such as session stores and real-time analytics.
For real-time data stream processing, Redis (since Redis 5) has introduced a new data structure, called `Redis Streams`, where you can do a lot more than what was possible with Pub/Sub, Lists or Sorted Sets. The best part of Redis Streams is that it’s built into Redis, so there are no extra steps to deploy or manage.
With `Redis Streams` and Golang, we can collect large volumes of data arriving at high velocity, communicate between producers and consumers asynchronously, manage our consumption of data even when producers and consumers don’t operate at the same rate and finally use the main memory efficiently.
What will you Learn:
In this workshop, we’ll walk you through the basics of how to use Redis Streams, and how consumer groups work, and finally show a working application that uses Redis Streams, in a Redis Cluster environment, using Golang.
Level: Intermediate, but beginners can easily participate.
TAGs: #SWCraftsmanship #Redis #RedisStreams #RealTimeAnalytics
Target audience: Intermediate/junior developers, architects, technical product managers who want to know the features of `Redis Streams`.
Prerequisites on Audience:
Development PC (any OS), docker engine and your favorite IDE (Visual Code will be used by presenter).
- Basic understanding of Go, some Redis and Streaming background would be helpful, but not mandatory. The goal is to explore and understand Redis Stream features and not to improve Golang skills.
Deliverables:
- Software developed during the workshop.
- The presentation presented during the workshop.
Schedule:
- Introduction about workshop, goals, etc. (including setup of your dev. environments, for those who are not configured already, Instruction will be released at least a month ago in github repo) – 10 min
- Presentation about Redis Stream (Including a couple of slides about streaming and how it is differentiated from Kafka, etc.) – 15 min
- Presentation about the use case scenario that will be implemented and tools – 10 min
- Exercise One – 10 min
- Exercise Two – 10 min
- Exercise Three – 10 min
- Questions – 10 min
- Concluding – 5 min
Total: 80 min