The article explains RocksDB’s LSM‑based architecture, column‑family isolation, and snapshot features, and shows how Vivo’s VPUSH mapping service uses these capabilities to store billions of registerId‑to‑ClientId mappings with high‑concurrency, low‑cost, fault‑tolerant performance across multiple replicated servers.
The article explains RocksDB’s LSM‑based architecture, column‑family isolation, and snapshot features, and shows how Vivo’s VPUSH MappingTransformServer uses these capabilities with C++ code to store billions of registerId‑to‑ClientId mappings across multiple replicated servers for high‑concurrency, low‑latency, and fast service expansion.
The article compares traditional relational databases with NoSQL, explains why NoSQL emerged, outlines its four main categories—key‑value, document‑oriented, column‑family, and graph databases—lists popular implementations, their features, and suitable and unsuitable application scenarios.
This article explains HBase’s data model and provides comprehensive table‑design strategies—including column‑descriptor options, row‑key best practices, high‑vs‑wide table trade‑offs, region splitting and pre‑splitting techniques—to help achieve optimal performance and scalability in large‑scale NoSQL workloads.
This article explains what NoSQL databases are, introduces the CAP theorem that underlies their design trade‑offs, outlines typical application scenarios, discusses their limitations, classifies the main NoSQL families, and reviews four widely used systems—Redis, HBase, Cassandra, and MongoDB.
This article explains the scenarios where HBase is appropriate, introduces core HTable concepts such as row keys, column families, columns, timestamps and values, and outlines design principles for schema and versioning to efficiently handle semi‑structured, sparse, multi‑version and massive data sets.
This article explains the limitations of traditional relational databases, introduces the emergence of NoSQL, categorizes its four main types—key‑value, document‑oriented, column‑family, and graph—detailing popular products, typical use cases, and scenarios where each is unsuitable.
This article compares traditional relational table design with HBase's column‑family model, showing how tables, rows, column families, and versioned cells are defined and how data is inserted using HBase's put commands.
This article explains why NoSQL emerged as an alternative to relational databases, outlines the four main NoSQL categories—key‑value, document, column‑family, and graph—describes their characteristics, typical use cases, and lists notable products and adopters.
