Choosing Between Driver‑Level and Proxy‑Level Database Middleware for Sharding

This article explains the different layers—encoding, framework, driver, proxy, and implementation—through which database sharding can be introduced, compares driver‑level and proxy‑level middleware, outlines their characteristics, common constraints, and provides a step‑by‑step process for planning, preparing, and executing a sharding project.

Database MiddlewareJavadriver layer

0 likes · 13 min read

Choosing Between Driver‑Level and Proxy‑Level Database Middleware for Sharding

Xiaohongshu Tech REDtech

Jul 4, 2022 · Databases

RedKV: Xiaohongshu's Distributed NoSQL KV Storage System

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.

Distributed KVLZ4 compressionNoSQL

0 likes · 25 min read

RedKV: Xiaohongshu's Distributed NoSQL KV Storage System

Tencent Music Tech Team

May 27, 2016 · Databases

Cross‑IDC Disaster Recovery Solution for KV Storage via a Proxy Layer

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.

KV storagecross-IDCdatabase

0 likes · 4 min read

Cross‑IDC Disaster Recovery Solution for KV Storage via a Proxy Layer