| name | lamport-formal-distributed |
| description | Design distributed systems in the style of Leslie Lamport, creator of Paxos, TLA+, and LaTeX. Emphasizes formal specification, logical time, and rigorous reasoning about concurrent systems. Use when designing consensus protocols or proving system correctness. |
| tags | paxos, consensus, tla+, formal-verification, logical-clocks, state-machine-replication, byzantine, distributed-transactions |
Leslie Lamport Style Guide
Overview
Leslie Lamport is a Turing Award winner who invented logical clocks, the Paxos consensus algorithm, TLA+ specification language, and LaTeX. His work forms the theoretical foundation of modern distributed systems.
Core Philosophy
"A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable."
"If you're thinking without writing, you only think you're thinking."
"The way to get correct programs is to first get something that is obviously correct and then make it efficient."
Lamport believes that distributed systems are too complex to reason about informally. Formal specification isn't optional—it's essential.
Design Principles
-
Formal Specification First: Write the spec before the code.
-
Time Is Logical, Not Physical: Use happens-before, not wall clocks.
-
Safety Before Liveness: First ensure nothing bad happens, then ensure something good does.
-
State Machines: Model systems as state machines for clarity.
When Writing Code
Always
- Write a formal specification (TLA+ or similar)
- Define safety and liveness properties explicitly
- Use logical timestamps for ordering events
- Model failures as part of the specification
- Prove correctness before implementing
- Consider all interleavings
Never
- Assume reliable networks
- Rely on synchronized clocks
- Ignore failure modes
- Test into correctness (testing finds bugs, not proves absence)
- Hand-wave about "eventual consistency"
Prefer
- State machine specifications
- Logical clocks over physical clocks
- Consensus protocols over ad-hoc coordination
- Formal proofs over informal arguments
- Explicit failure handling
Code Patterns
Logical Clocks (Lamport Timestamps)
class LamportClock:
def __init__(self):
self.time = 0
def tick(self):
"""Local event: increment clock"""
self.time += 1
return self.time
def send(self):
"""Send message: increment and return timestamp"""
self.time += 1
return self.time
def receive(self, msg_timestamp):
"""Receive message: max(local, received) + 1"""
self.time = max(self.time, msg_timestamp) + 1
return self.time
Vector Clocks (Causal Ordering)
class VectorClock:
def __init__(self, node_id, num_nodes):
self.node_id = node_id
self.clock = [0] * num_nodes
def tick(self):
"""Local event"""
self.clock[self.node_id] += 1
return self.clock.copy()
def send(self):
"""Send: increment own component"""
self.clock[self.node_id] += 1
return self.clock.copy()
def receive(self, other_clock):
"""Receive: element-wise max, then increment own"""
for i in range(len(self.clock)):
self.clock[i] = max(self.clock[i], other_clock[i])
self.clock[self.node_id] += 1
return self.clock.copy()
@staticmethod
def compare():
less = (a <= b a, b (vc1, vc2))
greater = (a >= b a, b (vc1, vc2))
less greater:
greater less:
less greater:
:
TLA+ Specification
--------------------------- MODULE SimpleConsensus ---------------------------
EXTENDS Integers, FiniteSets
CONSTANTS Nodes, Values
VARIABLES
proposed, \* proposed[n] = value proposed by node n
decided \* decided[n] = value decided by node n (or null)
TypeInvariant ==
/\ proposed \in [Nodes -> Values \union {NULL}]
/\ decided \in [Nodes -> Values \union {NULL}]
\* Safety: Agreement - all decided values are the same
Agreement ==
\A n1, n2 \in Nodes:
(decided[n1] # NULL /\ decided[n2] # NULL) =>
decided[n1] = decided[n2]
\* Safety: Validity - decided value was proposed
Validity ==
\A n \in Nodes:
decided[n] # NULL =>
\E m \in Nodes: proposed[m] = decided[n]
\* Liveness: Termination - eventually all decide
Termination ==
<>(\A n \in Nodes: decided[n] # NULL)
Init ==
/\ proposed = [n \in Nodes |-> NULL]
/\ decided = [n \in Nodes |-> NULL]
Propose(n, v) ==
/\ proposed[n] = NULL
/\ proposed' = [proposed EXCEPT ![n] = v]
/\ UNCHANGED decided
Decide(n, v) ==
/\ decided[n] = NULL
/\ \E m \in Nodes: proposed[m] = v
/\ decided' = [decided EXCEPT ![n] = v]
/\ UNCHANGED proposed
Next ==
\E n \in Nodes, v \in Values:
Propose(n, v) \/ Decide(n, v)
Spec == Init /\ [][Next]_<<proposed, decided>>
==============================================================================
Paxos Simplified
class PaxosNode:
def __init__(self, node_id, nodes):
self.node_id = node_id
self.nodes = nodes
self.promised = 0
self.accepted_num = 0
self.accepted_val = None
def prepare(self, proposal_num):
"""Phase 1a: Proposer sends prepare"""
responses = []
for node in self.nodes:
resp = node.handle_prepare(proposal_num)
if resp:
responses.append(resp)
return responses
def handle_prepare(self, proposal_num):
"""Phase 1b: Acceptor handles prepare"""
if proposal_num > self.promised:
self.promised = proposal_num
return {
'promised': True,
'accepted_num': self.accepted_num,
'accepted_val': self.accepted_val
}
return {'promised': }
():
responses = []
node .nodes:
resp = node.handle_accept(proposal_num, value)
responses.append(resp)
responses
():
proposal_num >= .promised:
.promised = proposal_num
.accepted_num = proposal_num
.accepted_val = value
{: }
{: }
():
n = .generate_proposal_number()
promises = .prepare(n)
([p p promises p[]]) <= (.nodes) // :
highest = (promises, key= p: p[])
highest[] :
value = highest[]
accepts = .accept(n, value)
([a a accepts a[]]) > (.nodes) // :
value
State Machine Replication
class ReplicatedStateMachine:
"""
Key insight: if all replicas start in the same state
and apply the same operations in the same order,
they will end up in the same state.
"""
def __init__(self):
self.state = {}
self.log = []
self.commit_index = 0
def apply(self, operation):
"""Apply operation to state machine"""
op_type = operation['type']
if op_type == 'set':
self.state[operation['key']] = operation['value']
elif op_type == 'delete':
self.state.pop(operation['key'], None)
elif op_type == 'increment':
key = operation['key']
self.state[key] = self.state.get(key, 0) + 1
def append_to_log(self, operation):
"""Add operation to log (not yet applied)"""
self.log.append(operation)
return len(self.log) - 1
():
.commit_index <= index:
.apply(.log[.commit_index])
.commit_index +=
Mental Model
Lamport approaches distributed systems by asking:
- What is the state? Define the state machine precisely
- What are the safety properties? What must never happen?
- What are the liveness properties? What must eventually happen?
- How do we order events? Logical time, not physical time
- Can I specify this formally? If not, I don't understand it
Signature Lamport Moves
- TLA+ specifications before implementation
- Logical clocks for event ordering
- Safety and liveness as separate concerns
- State machine replication for consensus
- Happens-before reasoning
- Formal proofs of correctness