0 views collected around this technical thread.
Kuaishou reduced half of its massive object storage expenses by redesigning its architecture to use HBase indexing, HDFS large‑file storage, MemoryCache, and a cross‑IDC LRC erasure‑coding warm layer that maintains disaster‑recovery while dynamically moving data from hot to warm to cold tiers.
This article explains how 360 Commercialization implements cross‑IDC hot‑standby for Kafka using MirrorMaker 2, covering MM2 fundamentals, architecture, internal topics, deployment on Kubernetes, design goals, solution details, challenges such as dynamic configuration and offset reverse‑mapping, and productized risk mitigation.
The article proposes a cross‑IDC disaster‑recovery architecture for key‑value stores that uses a storage proxy layer to record write logs in the primary data center, forward them to a read‑only backup center for replay, and route reads via load‑balancing, while noting current limitations such as complex configuration, low synchronization concurrency, and lack of multi‑write support.