ongaro-ousterhout-2014-raft

What problem does it solve?

This Skill translates the Raft paper's design principles into actionable guidance to reduce implementation complexity, eliminate brittle edge cases, and make distributed coordination predictable and maintainable for engineering teams.

Core Features & Use Cases

• Design-for-comprehension: Prioritizes understandability as a first-class objective when choosing protocols and trade-offs.
• Decomposition patterns: Prescribes separating leader election, log replication, and safety to minimize interdependency.
• State-space constraints & invariants: Recommends append-only logs, no-holes, monotonic terms, and explicit invariants to prevent pathological states.
• Randomization & recovery: Recommends randomized election timeouts, idempotent retries, majority quorums, and authoritative leader-driven recovery strategies.
• Use Cases: Architecting a fault-tolerant orchestrator, coordinating multi-agent systems, designing leader election and log replication for service clusters.

Quick Start

Apply Raft's leader-first decomposition and append-only log constraints to design a leader-based orchestrator that tolerates follower failures.