This article explains how Tencent’s cloud‑native message queue TDMQ, built on Apache Pulsar’s storage‑compute separation, meets financial‑grade reliability, strong consistency, horizontal scalability, and cross‑region disaster‑recovery requirements through a quorum‑based consistency model, multi‑protocol support, and read‑only broker design.
This article explains why locks are essential in programming, categorizes various lock types such as pessimistic, optimistic, spin, fair, reentrant, and distributed locks, and shows how to choose and implement them in Java for high‑concurrency, high‑availability, and high‑performance systems.
This article explains the fundamentals of Apache Kafka's consumer group rebalance protocol, covering partitioning, group coordination, JoinGroup and SyncGroup requests, heartbeat handling, common pitfalls, and best‑practice warnings for reliable streaming data processing.
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 comprehensive guide for Java backend interview preparation, covering essential framework experience, distributed technology basics, database performance tuning, core Java concepts, Linux log troubleshooting, and how to showcase practical project experience to stand out to interviewers.
This article presents a concise list of thirty practical architectural principles—ranging from simplicity and ROI to concurrency, statelessness, and user‑centered design—intended to guide developers and architects in creating maintainable, high‑quality, and scalable distributed software 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.
This article reviews common system‑wide unique ID generation techniques—including database auto‑increment, UUIDs, Redis counters, Twitter's Snowflake, Zookeeper sequences, and MongoDB ObjectId—detailing their advantages, drawbacks, optimization tips, and providing C# code examples for implementation.
This article introduces Kafka as a distributed messaging and stream‑processing platform, then enumerates the most important broker‑side configuration parameters—such as broker.id, log.dirs, zookeeper.connect, listeners, and retention settings—explaining their purpose and providing practical tuning advice for production environments.
This article explains the fundamental differences between RabbitMQ and Apache Kafka, covering asynchronous messaging patterns, the internal architectures of both systems, their respective strengths and weaknesses, and guidance on choosing the appropriate solution for various scenarios.
The article explains the “ghost replay” problem—an inconsistency arising from the third state of distributed requests—and examines how consensus protocols such as Paxos, Multi‑Paxos, Raft, and ZAB address it through epoch IDs, noop entries, and leader election rules to prevent duplicate log entries.
This article details a backend engineering practice that simulates 100 billion shake‑red‑packet requests by building a single‑machine prototype supporting one million connections, achieving peak QPS of 60 k, and demonstrates the methodology, hardware setup, code design, monitoring, and performance analysis.
Generating globally unique IDs in distributed systems requires balancing uniqueness, monotonicity, high availability, security, and storage efficiency, and this article compares common solutions—including database auto‑increment, Redis/MongoDB/Zookeeper, UUID versions, and the Snowflake algorithm—detailing their advantages, drawbacks, and practical implementation tips.
The article explains how Alibaba introduced systematic capacity planning, four‑stage capacity assessment, various single‑machine stress‑test techniques, and a full‑link stress‑testing platform to reliably handle the massive traffic spikes of the Double‑11 shopping festival, while also describing a flexible traffic‑control framework to prevent overload and avalanche effects.
The article details Ant Financial’s large‑scale, financial‑grade cloud‑native architecture and its Service Mesh implementation during the 2019 Double 11 shopping festival, describing the evolution from monolithic to distributed systems, the challenges of mesh adoption, and the operational benefits achieved.
This article explains how to build a high‑concurrency ticket‑seckill system using Go, Nginx weighted load balancing, and Redis, covering architecture design, local and remote stock deduction, Lua scripting for atomic operations, and performance testing with ApacheBench to achieve thousands of requests per second without overselling.
The Linux Foundation's newly created Reactive Foundation, backed by Alibaba, Facebook, Lightbend, Netifi and Pivotal, aims to accelerate Reactive Streams and RSocket standards, reshaping backend architectures with non‑blocking concurrency, functional programming models, and cloud‑native distributed communication.
The article distills years of Java backend experience into a concise checklist, showing how to replace JVM‑local locks with distributed locks, move thread‑blocked work to reliable message queues, model workflows with finite‑state machines, choose suitable inter‑service protocols, and always paginate queries to avoid memory and consistency problems.
This article presents a comprehensive Java architecture roadmap for developers with two to five years of experience, covering design patterns, engineering tools, distributed systems, micro‑services, performance tuning, low‑level fundamentals, and practical project experience while advising against side‑project distractions.
This article explains how to achieve eventual consistency for cross‑service transactions in a distributed environment by using RocketMQ's transactional messages, detailing the underlying principles, message flow, implementation steps for producers and consumers, and important usage limitations.
This article describes how a single‑machine prototype was built in Go to simulate a WeChat red‑envelope service capable of handling up to 6 × 10⁴ QPS, supporting one million concurrent connections, and processing 10 billion shake‑red‑envelope requests through careful load‑balancing, monitoring, and performance analysis.
This article summarizes the SOFAStack Cloud Native Workshop held at KubeCon China 2019, detailing Ant Financial’s journey from centralized to cloud‑native architectures, the open‑source SOFAStack ecosystem, and a hands‑on five‑hour demo that builds a micro‑service‑based online bookstore using Kubernetes, Service Mesh, Serverless, and distributed transaction technologies.
This article explains how Apache Kafka implements producer idempotence by introducing Producer IDs (PID) and sequence numbers, describes the request‑response flow for PID allocation, details server‑side PID management, shows the exact‑once guarantee mechanism, and answers common configuration questions with code examples.
The article explains Kafka’s master‑write master‑read architecture, why it does not implement a master‑write slave‑read model, the trade‑offs of consistency and latency, and how Kafka achieves load balancing through its leader‑replica design and operational safeguards.
This article traces the evolution of internet architecture from early software and open‑source phases through centralized monolithic designs to distributed and cloud‑native systems, highlighting challenges such as massive user scale, continuous delivery, DevOps automation, container orchestration, micro‑services, and the shift toward resilient, scalable cloud‑native solutions.
This guide outlines essential Java engineering skills—from distributed architecture and algorithms to advanced JVM concepts—and provides a curated collection of recent Alibaba interview questions to help developers with 1‑5 years of experience prepare effectively.
The article describes the challenges of handling book outbound operations—matching SN codes, ensuring data consistency, and avoiding lock contention—and outlines a comprehensive refactor that separates business logic, standardizes APIs, adopts asynchronous processing, and leverages Redis sets to achieve high‑performance, reliable SN allocation.
This article explains the concept of idempotence, provides real‑world examples such as duplicate form submissions and payment requests, and details practical backend techniques—including query handling, unique indexes, token mechanisms, pessimistic and optimistic locks, distributed locks, and API design—to guarantee that repeated operations produce consistent results without side effects.
This article curates a comprehensive list of technical resources covering backup system architectures, distributed technology designs, cloud computing frameworks, high‑performance computing, storage solutions, server virtualization, networking, big data, databases and AI, providing readers with links to in‑depth analyses and best‑practice guides.
The article explains the causes of service avalanche in distributed systems—especially cache avalanche—and presents comprehensive mitigation strategies such as diversified cache expiration, circuit‑breaker, isolation, and rate‑limiting techniques to keep applications resilient under load.
The article explains the mathematical definition of idempotency, its importance in preventing duplicate operations such as repeated payments or order creation, and presents practical strategies—including unique business IDs, optimistic locking, deduplication tables, distributed locks, token mechanisms, and payment buffering—to achieve reliable idempotent behavior in backend services.
This article examines three common cache‑update strategies, explains why some lead to data inconsistency, and proposes practical solutions such as delayed double‑delete, asynchronous retries, and message‑queue based recovery to maintain cache‑database consistency in high‑concurrency systems.
This article explains how WeChat redesigned its red‑packet system for the 2016 Chinese New Year, detailing the dual‑data‑center architecture, order and user data separation, caching layers, traffic routing, high‑concurrency controls, database sharding, and graceful degradation to handle tens of billions of requests per minute.
This article explains how to design a distributed backend that ingests millions of clicks per second, stores data with Kafka and HDFS, computes top‑N articles using sliding windows and periodic aggregation, handles node failures, and mitigates click fraud, all while balancing accuracy and resource usage.
This article compares three popular service discovery solutions—Zookeeper, etcd, and Consul—detailing their architectures, features, integration methods, strengths, and weaknesses, and concludes with a recommendation for using Consul in multi‑data‑center environments while noting its real‑time notification limitations.
The article investigates a Kafka cluster outage where several brokers became unavailable and consumers could not join groups, explains the role of __consumer_offsets, analyzes the coordinator selection logic, identifies a stuck loadGroupsForPartition operation and compact thread failure, and documents the recovery steps taken.
Meituan’s settlement and reconciliation platform was rebuilt from a single‑threaded, month‑end batch system into a distributed, multi‑threaded, real‑time service that abstracts core models, uses lock‑free processing, sharding, and dedicated Kafka topics, achieving millisecond latency for millions of daily bills across 17 business lines.
This article describes the background, requirements, existing industry solutions, and the final optimized implementation of a high‑performance, globally unique user ID generator based on MySQL auto‑increment, Redis, and atomic memory segments, including performance results from production deployment.
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 describes Ctrip's design of a distributed, globally unique user ID generator for MySQL migration, covering requirements, evaluation of common approaches such as auto‑increment, UUID, Snowflake and Redis, and detailing the final Flicker‑based solution with segment caching using AtomicLong to achieve high concurrency and reliability.
This article surveys various distributed unique ID generation techniques—including Oracle auto‑increment, Redis batch allocation, UUID versions, Hibernate and MongoDB strategies, and Twitter’s Snowflake—explaining their structures, trade‑offs, and practical implementation considerations for reliable, collision‑free identifiers.
This article explains Kafka end‑to‑end auditing, compares three products (Chaperone, Confluent Control Center, Kafka Monitor), describes timestamp and index embedding techniques, and outlines their architectures, metrics, and implementation details for detecting data loss, duplication, and latency.
This article provides a step‑by‑step analysis of Dubbo’s cluster fault‑tolerance mechanism, explaining the roles of Directory, Router, and LoadBalance, illustrating the execution flow with diagrams, and clarifying how invokers are selected and balanced in a distributed Java RPC framework.
This article presents a design for a transparent, flexible, and low‑resource distributed logging solution that uses Lucene for indexing, Apache Ignite for service and compute grids, and a custom Log4j2 appender, enabling fast, unified log queries across clustered applications.
This article details how Alibaba Group transformed its GitLab deployment from a single‑node bottleneck into a horizontally scalable, sharded architecture that handles millions of daily requests with high availability, improved performance, and robust data safety.
This article describes how Alibaba Group transformed its GitLab platform from a single‑node deployment to a distributed, sharded architecture with proxy services, performance optimizations, multi‑datacenter backup, and automated operations to support millions of users and dramatically increase request throughput.
This article explores how to build a high‑traffic insurance O2O platform for tens of millions of users by emphasizing simple micro‑service architecture, detailed functional requirements, performance targets, distributed storage, caching, service registration, and a practical technology stack for reliable, extensible backend development.
This article revisits the technical design and evolution of the 2015 Chinese New Year Gala "shake" activity, detailing how the backend architecture was progressively refined—from a simple prototype to a production‑grade system capable of handling tens of millions of concurrent requests—through resource pre‑download, access‑layer integration, load‑balancing, and robust fail‑over mechanisms.
The article explains the importance of configuration in software, distinguishes static and dynamic configuration, discusses the challenges of managing configuration in large distributed systems, and describes the evolution, design principles, and practical solutions of configuration centers such as Alibaba's Diamond.
The article presents a business‑oriented, three‑layer high‑availability architecture for a large‑scale game access platform, detailing measurable goals, client‑side retry with HTTP‑DNS, functional separation and degradation, multi‑region active‑active deployment, and automated, visual monitoring to achieve rapid fault detection, isolation, and recovery.
The article describes the high‑availability, high‑concurrency backend architecture of Weibo's paid reading and tipping platform, covering layered design, database sharding, asynchronous processing, monitoring, idempotency, distributed transaction handling, and security measures for a large‑scale internet‑finance system.
This article details Didi’s Passport authentication system architecture, describing how language migration, service decomposition, flexible ticket and SMS code designs, multi‑region active‑active deployment, an independent Argus access‑control layer, and interface splitting together achieve high availability and low latency under extreme traffic peaks.
This article reviews three open‑source Redis cache clustering approaches—Netflix's Dynomite, Twitter's Twemproxy, and Wandoujia's Codis—explaining their architectures, advantages, licensing, and suitability for production environments as alternatives to the native Redis cluster feature.
The article uses the Starbucks coffee‑making workflow as an analogy to explain how clustering, stateless task handling, service‑oriented design, asynchronous interfaces, and fault‑tolerant mechanisms together enable traditional systems to become highly scalable microservices on the cloud.
The article details how LeTV upgraded its payment platform in 2015 to handle up to 100,000 orders per second by implementing database sharding based on user IDs, a Snowflake‑style globally unique order ID, asynchronous consistency via message queues, multi‑level data caching, and high‑availability architectures for both master‑slave and load‑balanced deployments.
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.
This article recounts Zhihu's evolution from a tiny Python‑Tornado service on a single Linode to a massive, highly available backend employing custom logging, event‑driven processing, page‑render optimizations, and a service‑oriented architecture that now supports over 100 million users.
This article details JD.com's transition from static to dynamic, high‑performance product detail page architecture, describing the multi‑layer system design, data heterogeneity, caching strategies, scaling techniques, operational challenges, and the solutions implemented to meet rapid business demands during massive traffic events.
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.