cover photo credit - https://lightning.ai/pages/community/tutorial/redis-for-machine-learning/

Redis Streams feels safe. Messages get processed, you ACK them, and everything keeps moving. Nothing backs up, dashboards look clean, and your workers stay busy.

Then one day Redis starts behaving badly — not because of traffic, not because of a bug, but because memory quietly grew without anyone noticing. This post is about the assumption that caused that, and how Redis Streams actually behaves in production.

A practical, real-world approach to debugging Docker builds and containers that fail before they even start.

My constant quest for happiness keeps getting interrupted by perfection

How to use ansible for the first time

Let’s get this party started!