1 views collected around this technical thread.
This article explains Ozone's object storage architecture, its evolution of metadata management using distributed KV stores like Apache Cassandra, and the performance optimizations—read/write separation, unlimited scaling, and partitioning—that enable high‑throughput, low‑latency handling of massive datasets.
This article compares the consistency read mechanisms of the distributed key‑value stores Consul and etcd, detailing Consul’s three read modes and leader‑forwarding logic, and explaining etcd’s serialize and linearizable reads, including the internal notification and index‑checking processes.
RedKV, Xiaohongshu’s self‑developed distributed NoSQL key‑value store, combines a Redis‑compatible interface, RocksDB‑backed storage, and a shard‑managed multi‑cloud architecture that delivers three‑times higher write throughput, 1.5‑times read throughput, 40 % cost savings versus HBase, and sub‑5 ms P999 latency for petabyte‑scale workloads.
This article explains the core concepts and detailed design of a custom message queue built on a distributed key‑value store, covering terminology, architecture, broker metadata, topic metadata, message format, sending, storage, retrieval, delay handling, retry mechanisms, dead‑letter queues, and TTL policies.
This article presents a comprehensive case study of how WeChat Pay rebuilt its transaction record storage to handle massive data growth, improve performance, ensure data completeness, and strengthen security through a distributed key‑value architecture, hierarchical archiving, and robust operational safeguards.