Day 2 of 5
⏱ ~60 minutes
Distributed Systems in 5 Days — Day 2

Consensus Algorithms

Paxos basics, Raft leader election, log replication, safety guarantees

What You'll Cover Today

Day 2 of Distributed Systems in 5 Days builds directly on Day 1. You're moving from theory into applied practice. The concepts today require the foundation from yesterday, so if anything felt unclear, review it now.

ℹ️
Topics today: Raft, Paxos, leader election. Each section has code you can copy and run immediately.

Raft

Understanding Raft is the core goal of Day 2. The concept is straightforward once you see it in practice — most confusion comes from skipping the mental model and jumping straight to implementation. Start with the model, then write the code.

Raft
# Raft — Working Example
# Study this pattern carefully before writing your own version

class RaftExample:
    """
    Demonstrates core Raft concepts.
    Replace placeholder values with your real implementation.
    """
    
    def __init__(self, config: dict):
        self.config = config
        self._validate()
    
    def _validate(self):
        required = ['name', 'type']
        for field in required:
            if field not in self.config:
                raise ValueError(f"Missing required field: {field}")
    
    def process(self) -> dict:
        # Core logic goes here
        result = {
            'status': 'success',
            'topic': 'Raft',
            'data': self.config
        }
        return result


# Usage
example = RaftExample({
    'name': 'my-implementation',
    'type': 'raft'
})
output = example.process()
print(output)
💡
Key insight: When working with Raft, always start with the simplest possible case that works end-to-end. Complexity is easier to add than simplicity is to recover.

Paxos

Paxos is the practical application of Raft in real projects. Once you understand the underlying model, Paxos becomes the natural next step.

💡
Pro tip: When working with Paxos, always read the official documentation for the exact version you're using. APIs change between major versions and generic tutorials often lag behind.

leader election

leader election rounds out today's lesson. It connects Raft and Paxos into a complete picture. You'll use all three concepts together in the exercise below.

Common Mistakes on Day 2

📝 Day 2 Exercise
Consensus Algorithms — Hands-On
  1. Set up your environment for today's topic: install required tools and verify the basics work before writing any logic.
  2. Implement a minimal working version of Raft using the code example in this lesson as your starting point.
  3. Extend your implementation to incorporate Paxos — this is where the two concepts connect.
  4. Test your implementation with both valid and invalid inputs. What happens at the boundaries?
  5. Review your code: is there anything you'd name differently? Any function doing more than one thing? Refactor one thing.

Day 2 Summary

  • Raft is the foundation of today's lesson — understand it before moving on.
  • Paxos is how you apply it in real projects.
  • leader election ties the day's concepts together into a complete pattern.
  • Error handling and input validation belong in the first version, not as an afterthought.
  • Read error messages carefully — they usually tell you exactly what's wrong.
Challenge

Extend today's exercise by adding one feature that wasn't in the instructions. Document what you built in a comment at the top of the file. This habit of going one step further is what separates engineers who grow fast from those who stay stuck.

Finished this lesson?