2 views collected around this technical thread.
This article breaks down a mature e‑commerce platform into six layered modules—user reach, business operation, transaction fulfillment, supply chain, infrastructure, and BI—detailing core functions, design considerations, and data‑driven processes to guide scalable system design.
This article explains why queueing systems and rate‑limiting strategies are essential for AIGC platforms, describes the user‑facing product behaviors they produce, outlines design considerations, compares technical options, and provides practical implementation guidance to keep services stable, cost‑effective, and user‑friendly.
This article examines three strategies for checking username uniqueness at massive scale—direct database queries, Redis caching, and Bloom filter techniques—detailing their implementations, performance trade‑offs, memory consumption, and suitability for billions of users.
This article examines the difficulties of adding new fields to a core billion‑row MySQL table—including locking, page splitting, and index degradation—and presents a configuration‑driven, three‑layer architecture that uses JSON extension fields, extension tables, and Elasticsearch to achieve safe, scalable dynamic schema evolution.
This article explores how to build a scalable, high‑performance leaderboard for hundreds of millions of users by comparing traditional database ORDER BY approaches with Redis sorted sets, addressing challenges such as hot keys, memory pressure, persistence risks, and presenting a divide‑and‑conquer implementation strategy.
This guide demonstrates how to horizontally scale a Redis cluster by adding nodes as masters or slaves, configuring them, using redis-cli commands to join or remove nodes, and handling special cases such as removing a failed node, all with practical code examples.
This article objectively compares middleware‑based sharding with NewSQL distributed databases, examining their architectural differences, transaction models, high‑availability mechanisms, scaling, SQL support, storage engines, and maturity to help practitioners decide which approach best fits their workload and operational constraints.
The article examines Meta’s warning that current microservice architectures will struggle with the upcoming AI explosion, outlines the performance, scalability, and cost challenges, and proposes serverless, service mesh, and hybrid redesigns as potential solutions.
The article explains RocketMQ NameServer's lightweight, stateless design, its core routing and metadata management functions, AP‑oriented architecture, fault‑tolerant mechanisms, scalability features, and practical optimization techniques for high availability and low operational cost.
This article explains the concept of rate limiting in system design, covering its importance, common use cases, various types, popular algorithms such as token bucket and leaky bucket, implementation across different system layers, and the challenges associated with configuring and scaling rate‑limiting solutions.
The article chronicles Douyin’s journey from a modest early‑stage architecture to a sophisticated, distributed, micro‑service and cloud‑native infrastructure that leverages load balancing, caching, big‑data frameworks, CDN, edge computing, and automated operations to support billions of users and massive traffic spikes.
This article analyzes the essential requirements of massive‑scale game leaderboards, explains how Redis sorted sets and hash tables provide fast ranking and lookup, and presents a multi‑layered architecture—including hot‑key sharding, dynamic partitioning, tiered storage, read/write separation, pipeline batching, and hybrid persistence—to achieve real‑time, billion‑user performance.
Kafka 4.0 marks a milestone release that replaces ZooKeeper with the KRaft consensus engine, improves scalability and performance, introduces a server‑side consumer‑group protocol, adds shared‑group queue capabilities, and updates Java requirements and documentation, delivering a more robust and flexible streaming platform.
This article explains MySQL's replication mechanism, detailing master‑slave architecture, key threads, binlog formats (statement, row, mixed), common application scenarios such as backup, read/write splitting, and data migration, and highlights important considerations like network latency, consistency, delay, and security.
The article objectively compares NewSQL distributed databases with middleware‑plus‑sharding solutions, covering architectural differences, distributed transaction handling, high‑availability, scaling, SQL support, storage engines, maturity, and provides a decision‑making checklist to help engineers select the most suitable approach for their workloads.
This article explains how modern data‑intensive applications are built, detailing a complete data‑flow architecture—from API requests, caching, database queries, change capture, search indexing, and message queues—to core system concerns such as reliability, scalability, and maintainability, offering practical insights for architects.
The article describes the evolution from modular push modules to a framework‑based and finally a service‑oriented unified push platform, detailing its architecture, functional and non‑functional requirements, component responsibilities, and deployment considerations for high‑performance, scalable enterprise notification systems.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectures, distributed transaction support, high availability, scaling, SQL capabilities, and maturity to help readers decide which approach best fits their workload and operational constraints.
An in‑depth comparison of NewSQL databases and middleware‑based sharding reveals each approach’s architectural strengths, distributed transaction handling, scalability, HA mechanisms, storage engine design, and ecosystem maturity, guiding readers on when to adopt NewSQL versus traditional sharding solutions.
This article analyzes how Tencent Channel builds a scalable Feeds system for a massive multi‑level community by presenting a three‑layer architecture, core design principles, and read/write diffusion strategies to handle sub‑channel lists, post squares, and personal feeds while mitigating empty‑pull and moderation challenges.