1 views collected around this technical thread.
The article analyzes data‑consistency challenges caused by RPC timeouts, especially when interfaces lack idempotency or idempotency fails, and presents a lightweight mock/spy utility that can intercept, mock, or spy on service calls to quickly restore consistency in distributed systems.
This article presents a Kafka‑Proxy solution that enhances cluster availability, traffic governance, seamless cluster switching, near‑source production/consumption, non‑disruptive offset resetting, and message flow control through metadata sharing and a lightweight proxy layer.
The article surveys common global ID generation strategies for distributed systems—database‑managed approaches like MySQL auto‑increment and MyCat‑Zookeeper, and Java‑based methods such as UUID, Snowflake, Leaf, Redis INCRBY and direct Zookeeper—comparing their trade‑offs and recommending Leaf (segment or Snowflake mode) or MyCat‑Zookeeper for reliable, scalable identifiers.
This article details how Meituan's Kafka platform, serving over 15,000 machines and handling petabytes of daily traffic, faces read/write latency, slow nodes, and large‑scale cluster management challenges, and describes a series of application‑layer, system‑layer, and operational optimizations—including disk balancing, migration pipelines, fetcher isolation, consumer async, SSD caching, isolation strategies, full‑link monitoring, lifecycle management, and TOR disaster recovery—to improve performance and reliability.
The article details the design and implementation of a pickup‑code system for SaaS e‑commerce platforms, covering simple single‑table approaches and a globally unique 8‑digit code scheme that embeds database and table identifiers, with strategies for sharding, conflict resolution, dynamic routing, and extensible tenant‑specific configuration.
This article details how a membership system serving billions of users achieves high performance and high availability through a dual‑center Elasticsearch cluster, traffic‑isolated ES clusters, Redis cache with distributed locks, MySQL dual‑center partitioning, and fine‑grained flow‑control and degradation mechanisms, all while ensuring zero‑downtime migrations and consistent data.
This article explains the core principles and a range of consistency protocols—including CAP, ACID, BASE, 2PC, 3PC, Paxos, Raft, Gossip, NWR, Quorum, and Lease—detailing their roles, mechanisms, trade‑offs, and typical use cases in distributed systems.
This article provides an in‑depth overview of microservice concepts, motivations, architectural principles, design patterns, service splitting strategies, essential infrastructure, popular frameworks such as Spring Boot, Spring Cloud, Dubbo, and Service Mesh, and practical recommendations for adopting microservices in real‑world projects.
The article details how Xianyu’s 2020 messaging failures—lost messages, wrong avatars, and order status errors—were traced to duplicate IDs, push‑logic mismatches, and client bugs, and solved by introducing global UUIDs, ACK‑based retries, hierarchical conversation models, hybrid storage caching, and real‑time monitoring, boosting delivery reliability above 99.9%.
The article explains why idempotency is essential for reliable services, describes how unique identifiers such as UUIDs, Snowflake IDs, and database‑generated keys can be used to achieve it, and offers practical guidance on shared storage, avoiding unnecessary queries, and handling duplicate requests in distributed systems.
This article provides a thorough overview of distributed systems, explaining their definition, when to adopt them, core concepts like partition and replication, common challenges, essential properties, typical architectural components, and practical implementations to help readers build a solid learning roadmap.
The article explains the need for rate limiting in high‑traffic scenarios, describes common algorithms such as token‑bucket and Guava RateLimiter, compares single‑node and distributed implementations, and outlines a Redis‑based solution for precise flow control across multiple service instances.
This article details how Kuaidi Dache scaled from 2013 to 2015 by addressing LBS performance limits, redesigning long‑connection services, refactoring monolithic code into layered services with Dubbo and RocketMQ, building a secure open platform, implementing Storm‑based real‑time monitoring, and migrating data storage to sharded MySQL, Canal‑driven sync, and HBase for massive scalability.
The article details Douban's comprehensive platform architecture, describing its online load‑balancing layer, the BeansDB key‑value store, the internal DAE PaaS, the big‑data DPark engine, and the team and operational practices that support both online and offline workloads.