JIMDB, a Redis‑based distributed cache, introduces the Big‑Hot Key concept and a multi‑layer proactive governance framework that dynamically identifies resource‑intensive keys, automatically mitigates them, and delivers up to an 80% performance gain while dramatically improving system stability.
JIMDB, a high‑performance Redis‑based distributed cache, introduces the “Big‑Hot Key” concept to dynamically identify keys that strain CPU or bandwidth, and implements a multi‑layer active governance framework—including real‑time detection, server‑side caching, circuit‑breaker, and client‑side consistency—to dramatically reduce resource consumption and boost throughput.
This article details JD's end‑to‑end design of a real‑time browsing record platform that captures, stores, and queries up to 200 recent items per user with millisecond latency, covering architecture, hot‑cold data separation, microservice APIs, and streaming pipelines using Kafka, Flink, Jimdb, and HBase.
The article describes JD's real-time browsing record system architecture, detailing its four modules—storage, query, real-time reporting, and offline reporting—along with hot‑cold data separation, use of Jimdb, HBase, Kafka, and Flink to achieve millisecond‑level latency and high throughput for billions of user records.
This article describes how JD.com redesigned its product detail page system from a static, cache‑heavy architecture to a fully dynamic, multi‑level cached service using Nginx+Lua, JIMDB, and asynchronous workers, addressing scalability, performance, and high‑availability challenges for billions of daily page views.
This interview with JD’s distributed cache and NoSQL lead reveals how JimDB evolved from a Redis‑based engine to a two‑tier SSD‑optimized key‑value store, detailing fault‑tolerant design, online migration, scaling strategies, and the shifting role of DBAs in massive e‑commerce traffic.
