Common Pitfalls and Core Concepts of Distributed Systems, Message Queues, Caching, Sharding, and Transactions

Overview

The article introduces distributed systems using a Naruto analogy, defining them as a set of independent computers that cooperate to appear as a single service and highlighting their advantages and drawbacks.

CAP and BASE Theories

It explains the CAP theorem (Consistency, Availability, Partition tolerance) and the BASE model (Basically Available, Soft state, Eventually consistent), showing how real‑world systems trade off these properties.

Message Queue Pitfalls

Key issues such as non‑idempotence, message loss, out‑of‑order delivery, backlog, expiration, and queue saturation are discussed for RabbitMQ and Kafka . Mitigation strategies include using transaction or confirm modes, designing idempotent consumers, persisting messages (setting deliveryMode=2 ), configuring replication factors, and managing consumer ACKs.

Distributed Cache Pitfalls

The article examines Redis high‑availability via the sentinel mechanism, describing failure scenarios (master crash, asynchronous replication, split‑brain) that can cause data loss and recommending configuration of min‑slaves‑to‑write and min‑slaves‑max‑lag to reduce risk.

Sharding (Database Partitioning) Pitfalls

It distinguishes vertical and horizontal splitting, outlines challenges such as cross‑shard queries and transaction consistency, and reviews unique ID generation methods—auto‑increment, UUID , timestamp‑based IDs, Snowflake , Baidu UIDGenerator , and Meituan Leaf‑Snowflake —highlighting their trade‑offs.

Distributed Transaction Pitfalls

Various approaches are covered: XA two‑phase commit, TCC (try‑confirm‑cancel), SAGA, reliable message (prepared/commit) and max‑effort notification. For each, the principle, suitable scenarios, advantages, and drawbacks are summarized.

Finally, the article advises that adopting distributed architecture should be based on business needs, team capability, and cost considerations, and promises further deep‑dive posts on underlying principles and best practices.