Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Redis Lab and StackExchange.Redis: Docker, redis-cli, Redis Insight, ConnectionMultiplexer and Key Design
In StackExchange.Redis there should be one ConnectionMultiplexer per application: each multiplexer opens two connections, so creating one per request turns 200 requests into 400 connections and replies ten times slower. With real output: a compose lab with Redis 8 and Valkey 9, redis-cli latency modes, an unread MONITOR eating 101 MB, Redis Insight, RESP3 and the separate pub/sub connection, a 300x gain from pipelining, a 110-second timeout from sync over async, and listing keys with SCAN.
What Is Redis Beyond a Cache? The In-Memory Data Structure Server, Use Cases and Licensing
Redis is an in-memory server that keeps data structures, from strings to streams, under keys and runs commands one at a time on a single main thread; that is why every command is atomic and why one long command makes everyone wait. With real measurements: a 105 ms KEYS stalling another client's PING, 100,000 INCRs without a lock, server time versus round trip, a map of uses beyond caching, where Redis is a poor fit, the licensing history and how Valkey differs.