This article explains what cache breakdown is in high‑traffic scenarios, why it can overload databases, and presents practical solutions such as pre‑warming hot data, scheduled cache refreshes, and multi‑level caching with code examples in Java and Redis.
The article explains how Redis eviction policies work, why configuring maxmemory and a proper policy is essential to avoid OOM crashes, details each of the eight policies, shows practical configuration and monitoring commands, and dives into the source‑code implementation of LRU/LFU eviction.
The article details a founder's implementation of a ten‑agent AI team using the open‑source Clawdbot (now OpenClaw) framework, describing its architecture, cost‑saving heartbeat mechanism, Mission Control collaboration platform, and a concrete workflow that lets the agents autonomously produce competitive analyses, marketing content, and code tasks for a company.
This article walks through the design and implementation of a production‑ready article interaction system—including likes, collections, and reads—using Go, Gin, Redis, MySQL, Kafka, and Vue, covering architecture, data modeling, high‑concurrency handling, idempotency, rate limiting, and reconciliation.
This article walks through converting a single‑service article interaction module—handling likes, favorites, and reads—into independent microservices deployed on Kubernetes, detailing architecture goals, service separation, Redis‑based high‑concurrency handling, Kafka async persistence, deployment configurations, auto‑scaling, and real‑world performance results.
In a candid blog post, Redis founder Salvatore Sanfilippo admits he’s “surrendered” to AI, showing how Claude Code helped him refactor a library, fix transient bugs, build a C‑based BERT inference engine, and rewrite Redis Streams in minutes, arguing that manual coding is no longer the wise choice for most projects.
This article explains the Redis split‑brain problem that can occur in master‑replica clusters, outlines the interview points interviewers look for, and provides a detailed solution using the min‑replicas‑to‑write (or min‑slaves‑to‑write) configuration to sacrifice write availability for data consistency, along with best‑practice recommendations and common pitfalls.
This guide introduces Valkey Glide PHP, the official high‑performance PHP client for the Valkey in‑memory datastore, explains its core Rust‑based architecture, shows three installation methods, highlights key features such as cluster‑aware commands and TLS, and provides ready‑to‑run code examples for single‑node and clustered environments.
This article walks through the design patterns, three‑level loading mechanism, and practical implementation steps for integrating reusable, domain‑specific Skills into an existing Agent system, covering both local and distributed deployments with Redis‑based versioning and sandboxed execution.
The article examines the two most dangerous production failures in Redis high‑availability—split‑brain and replication storm—explaining their causes, real‑world impact, and practical engineering safeguards such as write‑protection parameters, network isolation, backlog sizing, and cascading replication.
Choosing a Redis persistence strategy requires balancing data reliability, recovery speed, performance impact, and storage cost, and this guide compares RDB, AOF, and hybrid approaches, provides configuration examples, and outlines best practices for production, backup, and Kubernetes deployments.
This article examines the common data‑consistency challenges when writing to both a database and a Redis cache, evaluates four write‑order strategies, and presents the most reliable approach—writing to the database first then deleting the cache—along with retry mechanisms using scheduled jobs, message queues, and binlog listeners.
This article examines the double‑write consistency problem between databases and caches like Redis, explains why naïve cache‑first or DB‑first updates can cause stale or phantom data under high concurrency, and evaluates four practical solutions with detailed trade‑offs and recommended retry mechanisms.
This article walks through why using a Redis Set for 200 million daily active users consumes 6‑8 GB of memory, how switching to a sharded Bitmap reduces usage to about 24 MB, and how Roaring Bitmap and ClickHouse further optimize sparse data and analytical workloads.
This article breaks down the interview‑level system design of a WeChat‑style step leaderboard that must support over a billion users, handling massive write spikes, low‑latency friend ranking queries, storage scaling, and relationship complexity with a three‑part architecture using MQ, Redis, and MySQL.
Learn a practical approach to count online users in real time by leveraging Redis sorted sets (zset) with SpringBoot, covering user identification via tokens or browser fingerprinting, key Redis commands (zadd, zrangeByScore, zremrangeByScore, zrem), and scheduled cleanup logic.
This guide walks through Redis's evolution from single‑node replication to Sentinel and native Cluster, explaining each architecture's principles, configuration steps, advantages, drawbacks, performance trade‑offs, and practical deployment recommendations for building highly available and scalable caching systems.
Redis stores data in memory, so when usage reaches the maxmemory limit it triggers one of six eviction policies—noeviction, allkeys‑lru, volatile‑lru, allkeys‑random, volatile‑random, and volatile‑ttl—each suited to different scenarios, and can be set via redis.conf or CONFIG SET, as illustrated with a Java Jedis example.
The article presents a ten‑step architecture for implementing scalable LLM Skills, covering a meta‑tool pattern to avoid tool explosion, progressive three‑level loading to save tokens, script execution outside the LLM context, Redis‑based storage with pub/sub updates, version locking, dynamic addition, batch loading, and file‑system strategies.
This guide explains why @Scheduled jobs run on every Spring Boot instance in a cluster, and presents three practical solutions—Spring Integration's Redis lock, Redisson, and ShedLock—complete with Maven dependencies, configuration snippets, code examples, and runtime screenshots to guarantee that only one node executes the scheduled task at a time.
Redis uses both time‑based and lazy expiration, marking keys as expired at their TTL but only removing them on the next access or during periodic cleanup, so expired keys are not deleted the instant they expire.
The author explains why state-owned enterprises are not always stable, why their low‑tech projects hinder interview performance, and offers concrete steps—such as adding Redis caching, multithreading, and using the STAR method—to turn a modest Java background into compelling interview material.
This article examines strategies for low‑latency, consistent hot‑account updates under high concurrency, comparing optimistic DB locking, Redis‑based deduction with asynchronous merging, data sharding, and MQ‑driven batch processing, and also addresses read‑side solutions.
This article explains how e‑commerce flash‑sale systems handle extreme concurrency by defining TPS requirements for different scales, applying a layered filtering architecture, and using techniques like CDN caching, rate limiting, Redis pre‑deduction, and minimal database writes to ensure stability.
During a Spring‑based interview platform project, the author discovered four typical bugs introduced by Claude Code—transactional self‑invocation loss, AI‑generated NullPointerExceptions, async task failures after entity deletion, and Redis Stream message buildup—and explains the root causes and concrete remediation steps.
This article presents a comprehensive, end‑to‑end solution for preventing duplicate consumption in RabbitMQ by combining architecture design, routing strategies, idempotent controls, state machines, and ACK mechanisms, and details six concrete implementation options with code examples.
This article explains how Redis handles concurrency, clarifying that core command processing remains single‑threaded while multi‑threaded I/O was introduced in Redis 6.0, and provides interview insights, architectural evolution, configuration examples, best practices, and common pitfalls.
The article compares four user‑level rate‑limiting approaches—Sentinel hotspot parameters, Sentinel ordinary flow control with cluster mode, Redis ZSet + Lua scripts, and Guava RateLimiter—explaining why Sentinel is unsuitable for long‑window low‑frequency limits and why Redis + Lua is the optimal solution for high‑traffic e‑commerce scenarios.
This article explains how to design a highly available service registry for microservice architectures, covering high‑availability mechanisms, performance optimizations, scalability strategies, core registry functions, and provides a complete Java Spring Boot implementation using Redis.
By combining a local Caffeine cache, a remote Redis layer, and a MySQL database into a three‑tier cache pyramid, this guide shows how to reduce API response time from 28 ms to 2 ms, cut CPU usage by 35 %, and achieve up to 14‑fold performance gains, complete with configuration, code, and monitoring tips.
This article explains how to integrate a Human‑In‑The‑Loop (HITL) mechanism into ReactAgent, detailing the motivation, design of interaction, tool description, XML‑based UI rendering, Redis‑driven waiting loop, and the broader architectural parallels with design patterns and other agent frameworks.
This article shares a collected list of 2023 Tencent backend developer compensation packages—showing total first‑year offers starting above 40 W RMB—followed by detailed explanations of interview questions covering Redis caching, MySQL transactions, hot‑key detection, SQL injection, HTTP/HTTPS differences, API timeout troubleshooting, and microservice migration strategies.
This article explains how to implement cross‑platform caching in PHP using both file‑based storage and Redis, providing complete code examples, describing key functions for checking, reading, writing, and expiring cache entries, and highlighting compatibility considerations for different environments.
This guide outlines a complete backend architecture for high‑volume GPS data, detailing the overall system flow, technology stack choices, Maven dependencies, data models, Kafka producer/consumer configurations, SpringBoot controllers, asynchronous processing, Redis caching, health checks, Docker deployment, and performance tuning recommendations to ensure stability and scalability.
The article explains why adding Redis alone often remains slow, introduces a three‑level cache pyramid (L1 Caffeine, L2 Redis, L3 MySQL) built with Spring Boot 3, and shows how this design reduces request latency from 28 ms to 2 ms, cuts CPU usage by 35 % and achieves up to 14‑fold throughput improvement.
This guide explains how to boost Redis query per second (QPS) from 50,000 to 500,000 by applying horizontal sharding, read‑write separation with master‑slave replication, memory and data‑structure optimizations, and network‑level tuning, while providing concrete examples and configuration tips.
This article introduces JetCache, an open‑source distributed cache built on Spring and Redis, explains its core features and typical use cases, details the main API and annotation support, and provides a step‑by‑step SpringBoot integration guide with full code examples.
The article demonstrates how to combine Spring Boot 3, Caffeine local cache, and Redis into a three‑level cache pyramid, reducing API response time from 28 ms to 2 ms, cutting CPU usage by 35 %, and providing detailed configuration, code examples, performance benchmarks, and mitigation strategies for common high‑concurrency pitfalls.
This article details a Redis bucket‑based inventory deduction architecture that guarantees strong consistency while eliminating over‑sell and under‑sell, boosting hot‑spot deduction TPS and stability through a merge‑commit process and comprehensive module design.
After three months of preparation, a friend secured an offer from SF Express Technology with a base salary of 20k*15—well above the initially expected 15k—and the post shares the full set of interview questions that led to the success.
Faced with minutes‑long posting delays and exploding review costs in a fast‑growing social app, the team introduced 24‑hour shift staffing, a local blacklist stored in MySQL, an in‑memory Trie + Aho‑Corasick matcher, Redis‑driven hot updates and a machine‑audit fallback with a feedback loop, dramatically cutting latency, cost and false‑positives.
This article walks through building a Spring MVC interceptor that leverages Redis to enforce per‑IP request limits, explains configurable parameters, shows how to apply protection selectively via mapping rules or custom annotations, and discusses practical pitfalls such as sliding‑window logic, path‑parameter handling, and real‑IP detection.
This article explains how to build a lightweight, production‑grade idempotency middleware for Spring Boot 3 using AOP, a custom @Idempotent annotation, SpEL‑generated keys, and Redis atomic operations, covering architecture, core components, code examples, use cases, and performance characteristics.
This article examines three practical approaches—microservice isolation, Redis‑based whitelist, and gateway‑plus‑AOP—to prevent external exposure of internal APIs, compares their trade‑offs, and provides a complete SpringBoot implementation of the gateway‑AOP solution with code samples.
This article examines whether Redis can serve as a reliable message queue by exploring its List, Pub/Sub, and Stream data structures, comparing their features, limitations, and durability against professional brokers like Kafka and RabbitMQ, and offering practical usage guidelines.
This article breaks down Redis's nine data types, explains the underlying structures and typical scenarios for each, compares best‑practice usage, highlights interview focus points, and warns about common misconceptions to help developers choose the most efficient storage solution.
Redis achieves single‑machine million‑level QPS not merely because it stores data in memory, but through a tightly coordinated set of four core design principles—pure in‑memory operation, single‑threaded architecture, I/O multiplexing, and highly optimized data structures—that together deliver ultra‑low latency and massive throughput.
This guide explains why delayed messages are essential for distributed system stability, compares RabbitMQ's TTL+DLX and delayed‑message plugin, details RocketMQ's precise timing and delay‑level features, and offers custom Redis and time‑wheel solutions with practical Java code examples and deployment tips.
This guide compares four common distributed ID generation techniques—database auto‑increment, UUID, Twitter’s Snowflake, and Redis INCR—detailing their advantages, drawbacks, and ideal use‑cases, helping architects select the most suitable method for their system’s scalability and performance requirements.
This article examines whether Redis can serve as a reliable message queue by comparing its List, Pub/Sub, and Stream features against professional solutions like Kafka and RabbitMQ, covering usage patterns, code examples, performance trade‑offs, persistence, and handling of message loss and backlog.
This article explains how Redis master‑slave replication provides hot backup, read‑write separation, high availability, and horizontal scaling by detailing its three‑stage workflow, full and partial synchronization mechanisms, key configuration options, and practical analogies for clear understanding.
This guide explains how to achieve pagination and multi‑condition fuzzy queries in Redis by leveraging ZSet for ordered paging and Hash with HSCAN for pattern matching, detailing command usage, combination strategies, and performance optimizations such as temporary set expiration and data freshness handling.
This article walks through the evolution of Redis distributed locks—from basic SETNX mutual exclusion to atomic SET with expiration, Lua‑based safe unlocking, Redisson's WatchDog auto‑renewal, and the RedLock algorithm—highlighting pitfalls, best‑practice implementations, and interview‑style Q&A for robust production use.
Redis offers five core data types—String, Hash, List, Set, and ZSet—each acting as a high‑performance concurrent data structure that determines system throughput, latency, and stability; this guide explains their characteristics, optimal use‑cases, anti‑patterns, and practical code examples for robust architecture design.
This article dissects a production‑grade Go database access framework for microservices, covering unified interface abstraction, factory pattern for multi‑DB support, PostgreSQL array handling, read‑write splitting with load balancing, Redis cache protection, monitoring, and deployment considerations, with full code examples and open‑source links.
To reliably handle RocketMQ's at-least-once delivery semantics, this guide explains why duplicate consumption is inevitable, outlines three defensive layers—Redis‑based idempotency, database unique constraints, and state‑machine checks—provides production‑grade Java code, and details ACK/retry strategies and monitoring practices for robust systems.
This guide walks you through RedisInsight—a visual Redis GUI that supports clusters, SSL/TLS, and memory analysis—covering Linux installation, environment variable setup, service startup, Kubernetes deployment via YAML, and core usage such as browsing keys, executing commands, and monitoring performance.
This article explains how to protect Go services from overload by implementing HTTP request rate limiting using the standard token‑bucket limiter, per‑IP throttling with a map and mutex, and a distributed approach with Redis and Lua scripts, complete with practical code examples and middleware integration.
This guide explains how Redis implements distributed locks, outlines common pitfalls such as lock contention, zombie locks, and mismatched expiration times, and provides step‑by‑step solutions—including single‑node SET commands, Redlock high‑availability algorithm, Lua‑based safe release, and best‑practice recommendations for real‑world deployments.
This article walks through the strengths, typical use cases, and Python connection code for relational databases (MySQL, PostgreSQL, SQLite), NoSQL stores (MongoDB, Redis, Neo4j), cloud‑native options (DynamoDB), and emerging vector databases such as Milvus, helping you decide which fits your project.
This article breaks down the core concerns interviewers have for senior Go engineers—system stability, middleware pitfalls, Redis risk isolation, message‑queue buffering, distributed consistency, configuration management, ID design, and avalanche prevention—offering concrete insights and practical interview answers.
The article explains the delayed double‑delete cache‑invalidation pattern, its four major drawbacks in high‑concurrency environments, and presents four production‑grade alternatives—event‑driven binlog updates, distributed‑lock with versioning, write‑through proxy layers, and logical‑delete with async cleanup—used by leading Chinese internet firms to achieve reliable data consistency.
The article explains how Redisson implements a re‑entrant distributed lock using Redis hash structures and the atomic HINCRBY command to manage client identity, re‑entry counting, concurrency safety, and graceful release, providing a complete technical analysis with code, Lua scripts, and best‑practice guidelines.
Rudis v0.2.0 introduces a major architecture overhaul, upgraded Tokio runtime, shared‑nothing threading, master‑slave replication, transaction support, and a refactored KEYS command that boosts performance by up to 99.55% for large data sets.
Redis achieves sub‑millisecond response times by storing all data in RAM, using a single‑threaded event loop with I/O multiplexing (epoll/select/poll), and employing highly optimized data structures such as skip lists and hash tables that provide O(1) or O(log N) operations.
This article presents a systematic benchmark comparing ClickHouse, Doris, and Redis for IP‑range dimension lookups using Flink‑Kafka pipelines, detailing test design, result table schema, query interfaces, and performance results across varying data rates, concluding that Redis offers the fastest and most stable query latency.
This article explains why duplicate order requests occur, analyzes the idempotency challenges, and presents practical front‑end and Redis‑based solutions—including button disabling, SETNX locking, and token validation—to ensure only one successful order per user action.
This article explains the unique challenges of flash‑sale systems—massive, short‑lived traffic spikes—and presents practical backend optimizations such as front‑end request filtering, Redis‑based atomic counters, streaming queues, safe database updates, and unit‑level isolation for global deployments.
This step‑by‑step guide shows how to design, install, configure, start, and verify a Redis Sentinel high‑availability setup with one master, two replica nodes, and three sentinel monitors, including client connection examples and common troubleshooting tips.
This article explains why Redis cache penetration occurs and presents four practical mitigation techniques—using a Bloom filter, caching placeholder values, pre‑warming hot keys, and applying authentication with rate‑limiting—to protect backend performance and database stability.
Redis delivers millisecond‑level response and millions of operations per second by storing data entirely in memory, using a single‑threaded event‑driven model, efficient I/O multiplexing with epoll, and highly optimized data structures such as strings, hashes, lists, sets and sorted sets.
Redis has introduced a multithreaded query engine that dramatically reduces latency and increases throughput—up to 16×—for vector similarity searches, enabling vertical scaling and better support for real‑time RAG applications compared to traditional single‑threaded architectures and competing vector databases.
This article explains Redis master‑slave replication, covering its purpose for data redundancy, read/write separation, and high availability, and details the full‑synchronization and incremental‑synchronization processes with step‑by‑step diagrams.
This article outlines practical cache design principles, covering suitable scenarios, health metrics, common pitfalls like avalanche, breakdown and penetration, and concrete implementation rules for both local (Caffeine) and Redis caches to ensure microsecond‑level response and stable high‑traffic performance.
This article explains a flash‑sale system architecture from seven dimensions—including Nginx + CDN, routing with Redis, MQ clustering, business logic, read‑write‑separated databases, security controls, and page‑level optimizations—while providing concrete Nginx configs, Redis lock strategies, and database transaction tips to handle massive concurrent requests.
The article starts by highlighting Xiaomi's competitive software developer salaries, then provides a detailed Java interview guide covering reflection fundamentals, static vs dynamic proxies, SPI vs API, synchronization behavior, Redis caching strategies, and JWT authentication, complete with code examples and practical comparisons.
This guide introduces RedisInsight, a powerful Redis GUI, and provides step‑by‑step instructions for physical and Kubernetes installations, environment configuration, service startup, and basic usage including Redis setup and UI operations, all illustrated with code snippets and screenshots.
This article explains the principles and implementation details of common rate‑limiting algorithms—token bucket and sliding‑window counting—including their core concepts, key processes, Java code examples, and how to extend them to distributed scenarios with Redis Lua scripts.
This article explains why Redis can handle massive concurrent traffic by storing all data in RAM, using a single‑threaded event loop, leveraging Linux epoll for I/O multiplexing, and employing highly optimized in‑memory data structures that keep latency in the microsecond range.
This guide walks through installing RedisInsight on Linux, setting environment variables, launching the service, deploying it with Kubernetes, and using its GUI to monitor and manage Redis instances, complete with command examples and configuration details.
This article explains how to design a high‑concurrency ticket‑spike service that can handle millions of requests by using multi‑layer load balancing, Nginx weighted round‑robin, local stock caching, and atomic Redis operations, complete with Go code examples and performance testing.
This article explains when to store user objects in Redis as a JSON‑encoded String or as a field‑level Hash, comparing memory usage, atomic updates, network overhead, concurrency safety, scalability, and provides practical tips for large keys, hot keys, and Redis threading.
The article details Alibaba's 2024 campus backend salary bands, compares them with peers, outlines the interview process and project presentation tips, and provides in‑depth technical tutorials on Redis Lua scripts, cache consistency, slow‑query logging, MySQL optimization, Java reflection, WebSocket vs polling, SSE, TCP/UDP, and HTTP vs HTTPS.
This article explains Redis eviction policies, how the eviction process works, and practical solutions for cache penetration, breakdown, and avalanche, helping you select optimal strategies and mitigate high‑traffic cache failures.
This guide walks you through three practical Spring Boot solutions—database scheduled scans, message‑queue delayed queues, and Redis key‑expiration notifications—to automatically cancel unpaid orders after 30 minutes, complete with code samples, architecture diagrams, pros and cons, and best‑practice recommendations.
Learn how to design and implement a ready-to-use rule engine combined with a gray release system using Golang, Kafka, Redis, and CEL, complete with Docker‑compose deployment, edge execution, token‑bucket throttling, and webhook actions, plus full source code for a production‑grade marketing strategy platform.
Redis offers three persistence options—RDB snapshots, AOF command logging, and the hybrid RDB+AOF mode introduced in Redis 4.0—each with distinct workflows, configuration settings, advantages, and trade‑offs, and the article outlines their mechanisms, pros/cons, practical configuration tips, and deployment recommendations.
This article explains how Uber solves the "nearby driver" problem by employing the open‑source H3 hexagonal spatial index, hierarchical grids, Cassandra for persistent storage, and Redis caching to deliver fast, accurate, and scalable real‑time location services.
The article walks through a real‑world OOM incident in a high‑traffic hotel information service, detailing the root‑cause analysis of memory exhaustion, JVM heap configuration, GC behavior, heap‑dump inspection, and the concrete optimizations applied to prevent similar failures.
This article provides a comprehensive guide to Java concurrency and related concepts, covering synchronized lock upgrades, object vs class locks, lazy and double‑checked singleton implementations, ThreadLocal mechanics, reflection usage, annotation scopes, JVM class loading, and Redis cluster threading behavior.
Spring Boot 4.0, built on Spring Framework 7.0, introduces HTTP Service Clients, native API versioning, full JSpecify null‑safety, Java 25 support, upgraded dependencies, Gradle 9 compatibility, Redis static master‑replica configuration, and drops Undertow, with migration advice to move through 3.5 first.
Redis 6.0 adds a multithreaded network I/O model, client caching, ACL and RESP3, and explains why earlier versions were single‑threaded, how the new IO threads cooperate with the main thread, and the practical steps to enable and tune multithreading for better performance.
The article shares iFlytek's recent campus salary packages, then dives into a detailed Java interview guide covering Redis data types, key expiration handling, thread safety, ThreadLocal usage, MySQL covering and composite indexes, slow‑query analysis, and SQL‑injection prevention techniques.
This article details the three‑year evolution of a self‑built Redis service, covering its massive scale, architectural redesign, migration from LB to a custom DRedis SDK, same‑city active‑active near‑read support, Redis‑server version upgrades, instance specifications, proxy rate‑limiting, and extensive automation that together boost performance while cutting costs.
This article explains Redis master‑slave replication, detailing the full synchronization process that creates an RDB snapshot and streams buffered writes, as well as the incremental synchronization that resumes after a disconnection using PSYNC and the replication backlog.
This article walks through the design and implementation of a complete seckill (flash‑sale) system built on SpringBoot, MyBatis, MySQL, RabbitMQ and Redis, covering double MD5 password hashing, distributed sessions, unified exception handling, caching strategies, memory flags, pre‑decrement inventory, asynchronous order processing, oversell prevention, and rate limiting, with code snippets and UI screenshots.
This article compiles concise, high‑scoring answers to essential operations interview questions, covering security hardening, intrusion response, high‑availability architecture, disaster‑recovery design, Redis replication and clustering, Docker fundamentals and networking, Kubernetes components, monitoring, CI/CD pipelines, and the evolving role of DevOps.
A real‑world incident at JD Tech shows that a single 1.5 MB Redis cache key caused a full‑site outage during a high‑traffic event, and the article explains the underlying cache‑breakdown and bandwidth traps, then details three emergency mitigations and long‑term preventive practices.
This article explains Redis master‑slave replication, covering the roles of master and replica, the full‑copy synchronization process, the incremental sync mechanism, and the step‑by‑step workflow illustrated with diagrams to help engineers implement reliable high‑availability data stores.
This article explains Redis Pipeline’s core principle of batching commands to reduce network round‑trips, presents benchmark data showing up to 17‑fold speedups, details real‑world use cases such as cache warm‑up, heartbeat reporting, and high‑traffic events, and provides best‑practice guidelines on batch sizing, error handling, cluster constraints, and comparisons with transactions and Lua scripts.
