This article examines the various scenarios in which MySQL can lose data, covering InnoDB and MyISAM engine behaviors, flush policies, master‑slave replication pitfalls, XA transaction handling, and practical solutions to improve consistency and availability.
This article reviews essential distributed‑system concepts, including middleware roles, RPC communication steps, mobile‑agent characteristics, naming services, Petri‑net modeling, logical and vector clocks, consistency models, code migration, two‑phase and three‑phase commit protocols, and election and mutual‑exclusion algorithms.
This article outlines a comprehensive design for a high‑concurrency distributed backend system that handles tens of millions of page views, detailing group‑based data partitioning, master‑slave roles, consistency models, heartbeat services, and global coordination to achieve scalability and fault tolerance.
The article explains why consistency is essential in distributed systems, describes the CAP theorem, outlines various consistency models such as strong, weak, and eventual consistency, and discusses the trade‑offs between data correctness and system performance.
The article explains Amazon’s Dynamo distributed key‑value store architecture, covering its decentralized design, consistent hashing with virtual nodes, replication strategies, quorum‑based read/write parameters, vector‑clock versioning, failure detection, hinted handoff, scaling mechanisms, and how these techniques together provide high availability, scalability, and reliability.
FusionStorage is a distributed block storage solution for x86 servers that separates compute and storage, uses DHT‑based key‑value architecture, provides strong consistency and read‑repair mechanisms, and supports various cache media and advanced storage functions such as thin provisioning and synchronous replication.
This article explains why concurrent read‑write operations on a shared balance can cause inconsistencies, illustrates the problem with a purchase‑balance example, and shows how a Compare‑And‑Set (CAS) update clause guarantees atomicity and preserves data integrity.
The article analyzes the use of a master/slave architecture for distributed caching, explains why two clusters, CAS, and proxy are employed, discusses consistency and availability challenges, and evaluates possible mitigation strategies for cache failures.
This article systematically explores the distributed characteristics of NoSQL databases, covering consistency trade‑offs, replication techniques, anti‑entropy protocols, data placement strategies, failure detection, and coordinator election, while illustrating each concept with diagrams and practical examples.
This article examines the problems and trade‑offs of metadata protection in cloud object storage, highlighting the importance of reliability, availability, and consistency, and comparing primary‑secondary and multi‑replica models, including the WRN algorithm and practical operational considerations.
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 explores three core design semi‑principles—priority, consistency, and feel—explaining how they guide designers and product managers to allocate interface resources, maintain predictability, and create positive user emotions that can determine product success.
This article explores three essential UI design principles—priority, consistency, and feeling—explaining how they guide user decisions, reduce cognitive load, and create a satisfying experience, while offering practical tips for product designers and managers.
