This article explains five stability patterns—retry, timeout, circuit breaker, handshaking, and bulkhead—used to keep distributed systems resilient, illustrates their implementation with JAX‑RS/RESTful services in Java, and shows how asynchronous Java 8 techniques further improve reliability.
Distributed systems, long used since the 1970s and popularized by internet giants like Google, offer scalable, cost‑effective, and fault‑tolerant architectures by leveraging many low‑cost servers, emphasizing horizontal scaling, avoidance of single points of failure, minimal inter‑node communication, and stateless services for elastic application deployment.
This article presents a curated collection of seminal papers and resources covering operating systems, virtual machines, system design principles, distributed algorithms, overlay networking, and debugging techniques to help engineers deepen their understanding of system architecture and advance beyond growth bottlenecks.
The article explains the origins, core features such as scalability, cost‑effectiveness, fault tolerance, and elastic expansion of distributed systems, and outlines design philosophies like low hardware requirements, horizontal scaling, avoidance of single points of failure, minimized inter‑node communication, and stateless service architecture.
In this presentation, seasoned R&D engineer Bian Xuebin, who leads Suning’s object storage platform, shares the design principles and architectural strategies behind Suning’s multi‑tenant object storage system, illustrated through a series of detailed slides.
This article explains how LinkedIn uses Apache Kafka as a high‑throughput, fault‑tolerant messaging backbone, detailing its architecture, message categories, layered replication, audit mechanisms, and the engineering practices that keep billions of daily messages reliable and fast.
The 2015 Beijing QCon highlighted four technical talks covering asynchronous processing in distributed systems, the DRC data‑replication infrastructure, minute‑level high‑availability fault recovery, and cloud‑era database operations, illustrating Alibaba's approaches to scalability and reliability in modern cloud platforms.
This article provides a comprehensive overview of Apache Kafka, covering its origin, core design goals, key terminology, architectural components, message routing, consumer groups, delivery guarantees, and a detailed comparison with other popular message queue systems.
This article examines the objectives, challenges, evolutionary technologies, design principles, and practical strategies such as resource separation, caching, load balancing, database read/write splitting, CDN, distributed storage, and consistency models that are essential for building and scaling large‑scale website architectures.
This article examines how WhatsApp grew its user base, message volume, and infrastructure dramatically over two years while keeping the engineering team at ten, detailing the architectural choices, Erlang‑based stack, hardware scaling, decoupling strategies, and the operational challenges that led to both performance gains and a major outage.
The article revisits the CAP theorem, explains why the classic "two‑of‑three" interpretation is misleading, compares ACID, BASE and CAP, discusses the role of latency, and presents practical strategies for detecting, handling, and recovering from network partitions in distributed systems.
The article examines the challenges of scaling a single‑server data service, compares data partitioning and replication, explains consistency models, and surveys distributed transaction protocols such as 2PC, 3PC, Paxos, and Dynamo's NWR model, highlighting their trade‑offs in availability, consistency, and performance.
This article explains the consistent hashing algorithm, its motivation in cache systems, the concept of monotonicity, the step‑by‑step mapping process, and how virtual nodes improve balance and resilience when cache servers are added or removed.
A recent study of five major open‑source distributed systems reveals that most failures can be triggered and reproduced with simple, multi‑event tests, highlighting the importance of systematic testing, deterministic error handling, and concise logging for reliable system operation.
The article details Douban’s platform architecture, covering online services, the BeansDB key‑value store, the DAE PaaS layer, offline big‑data processing with MooseFS and DPark, and the team’s engineering practices that keep the system reliable and extensible.
The article examines the inevitability of service coupling in large‑scale web applications and proposes a two‑dimensional architecture that separates business and logic layers, uses internal data stores, introduces a naming‑and‑location service, selects appropriate transport and RPC protocols, and automates operations with health checks, load balancing, and failover to achieve continuous reliability.
The article traces web architecture’s evolution from simple single‑server Java/JSP sites through memory caching, load‑balanced multi‑machine logic, read/write separation, master‑slave replication or message‑queue syncing, horizontal/vertical sharding, and finally multi‑server web‑server deployments behind load balancers to achieve scalability and reliability.
This article surveys practical approaches for implementing real‑time collaborative editing, comparing simple edit‑lock methods, line‑based diff/patch techniques, character‑level Myer's diff, and Operational Transformation—including distributed challenges—and offers recommendations based on project size and performance needs.
