ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Redis Streams let you build a durable, parallel‑safe event pipeline. This blog walks through producing, consuming, and trimming streams, highlights memory and consumer‑group trade‑offs, and gives a clear call‑to‑action for prototyping in your own projects.
Learn how to set up a Redis Streams consumer group, acknowledge messages, and avoid common pitfalls that cause memory growth or missed processing.
Learn how the start ID in XGROUP CREATE decides whether a Redis Streams consumer group replays history or processes only new messages, with a concrete example and verification steps.
Redis Streams provide durable, ordered messaging with consumer‑group semantics. Learn the minimal design, trust boundaries, ops checks, and when to reconsider.
Gulp 4's stream pipeline and gulp.lastRun make incremental asset builds fast and readable — as long as you target Gulp 4 explicitly and don't ask it to bundle JavaScript.
Learn how Node.js stream backpressure works, why ignoring the write return value can exhaust memory, and see a concrete example of safely streaming a large file through a gzip transform while respecting drain events.
Learn how Redis Streams provide an append‑only log with consumer groups for at‑least‑once delivery, see a concrete setup example, and understand the trade‑offs to keep your system stable.
Learn how Redis Streams with consumer groups give you durable, exactly‑once processing for high‑throughput event streams, with a Python example and production‑tuning tips.
Learn how to create a Redis Streams consumer group, consume messages, acknowledge them, monitor pending entries, and recover from consumer failures using XCLAIM.
redis
gulp
nodejs