system-type-distributed Skill

Source

• Creator: microsoft
• Repository: microsoft/amplifier-bundle-systems-design
• Skill file: skills/system-type-distributed/SKILL.md

What it does

Foundational patterns for distributed systems — consensus, consistency models, replication, partitioning, clock synchronization, distributed transactions, and failure modes. Use when designing or evaluating any system that spans multiple nodes, processes, or failure domains.

Skill instructions

System Type: Distributed Systems Foundational patterns, guarantees, and failure modes for systems that span multiple nodes. --- 1. Consistency Models Most engineers say "consistent" when they mean five different things. Precision matters here because the guarantees determine what your application can and cannot assume. Linearizability What it guarantees. Every operation appears to take effect instantaneously at some point between its invocation and completion. All processes observe the same ordering. If operation A completes before operation B begins, B sees A's effects. What it costs. Requires coordination on every operation. In the presence of network partitions, a linearizable system must either become unavailable or violate the guarantee. Latency is bounded by the slowest participant in the quorum. Cross-datacenter linearizability is possible (Spanner does it) but requires specialized hardware (GPS + atomic clocks) and still adds measurable latency. When it's sufficient. Leader ele