Page 4 - Redis

Redis

AI generated

Pub/Sub for Real-Time Events Between Services

Maxim Mironjuk - July 24, 2025

Redis Pub/Sub distributes messages in real time to all currently connected subscribers, without storing them or giving any delivery guarantee. This fire-and-forget semantic makes Pub/Sub ideal for live notifications between services, but unsuitable for anything that needs persistence or guaranteed delivery.

Redis

AI generated

Backup and Restore Strategies for Production Redis Instances

Maxim Mironjuk - June 29, 2025

Persistence mechanisms like RDB and AOF protect against a process crash, but not against a failed disk, a deleted server, or a human mistake. A solid backup strategy for Redis copies snapshots consistently, automates retention, regularly tests restores, and keeps at least one copy outside the production infrastructure.

Redis

AI generated

Redis HyperLogLog for Approximate Counting

Maxim Mironjuk - May 18, 2025

Count millions of unique visitors without storing millions of individual IDs: HyperLogLog estimates the cardinality of a set with a fixed memory footprint of only 12 kilobytes and a typical error of about 0.81 percent, regardless of whether the set contains a thousand or a billion elements.

Magento Redis

AI generated

Redis Security Hardening for Production

Maxim Mironjuk - May 11, 2025

Redis is configured by default for maximum performance, not maximum security. Without authentication, with an open network bind and dangerous commands enabled, a production Redis instance becomes an easy target. This article shows the complete hardening process for Magento environments, from passwords and ACLs to TLS.

Magento Redis

AI generated

Redis vs. Varnish: Clear Roles in Magento

Maxim Mironjuk - May 09, 2025

Redis and Varnish are often pitted against each other in Magento discussions, yet they solve fundamentally different problems. Redis is the cache and session backend for object cache and full page cache storage, Varnish is the HTTP layer in front that delivers whole pages before Magento even starts. This article explains the clean role split.

Redis

AI generated

Master-Replica Replication in Detail

Maxim Mironjuk - May 08, 2025

Redis replication looks simple at first glance: one command, one connection, data flows from master to replica. Underneath, though, the PSYNC protocol decides whether a brief network interruption costs only a few kilobytes or requires retransferring the entire dataset, and an incorrectly sized backlog regularly wipes out exactly that advantage in practice.

Magento Redis

AI generated

Session Backend Tuning for Magento with Redis

Maxim Mironjuk - April 30, 2025

A misconfigured session backend is one of the most common yet hardest to diagnose causes of slow Magento shops. Session locking, timeout values and the break_after_frontend parameter decide whether parallel Ajax requests within a session block each other or run cleanly side by side. This article shows step by step how to correctly configure the Redis session backend.

Redis

AI generated

Data Loss Scenarios in Redis and How to Guard Against Them

Maxim Mironjuk - April 28, 2025

Data loss in Redis rarely comes from a single obvious mistake, but from the interplay of fsync timing, replication lag and automatic failover under time pressure. Knowing the concrete scenarios under which Redis actually loses data lets you deliberately combine the right safeguards, instead of relying on a single feature.

Magento Redis

AI generated

Redis Troubleshooting: Common Errors in Magento Environments

Maxim Mironjuk - April 07, 2025

When Redis causes trouble in a Magento environment, only a handful of error patterns are really common: refused connections, OOM errors on writes, and session lock timeouts during checkout. This article walks through each of these error patterns systematically, showing the diagnostic steps and the concrete fix.

Redis

AI generated

Preventing Cache Stampede: Locking and Probabilistic Refresh

Maxim Mironjuk - April 06, 2025

When a heavily requested Redis key expires, hundreds of concurrent requests often hit the database unchecked, because each request handles the cache miss independently. This phenomenon is called cache stampede or thundering herd and can be prevented deliberately with mutex locking or probabilistic early expiration, without giving up the benefits of the cache.