liveBook · Manning

Leader-follower topology

As explained in ScyllaDB in Action

A leader-follower topology assigns one node as leader with special responsibilities while other nodes follow its coordination.

A leader-follower topology gives one node special responsibilities and makes other nodes follow its coordination. Systems using this design elect a replacement leader when the current leader fails, allowing operations to continue. section 1.2.1

ScyllaDB takes a different approach: every node has equal status. A request can contact any node, which calculates the owning node and forwards the request without relying on a centralized leader. section 1.2.1

The topology implies:

  • Leader failure triggers leader election. section 1.2.1
  • Coordination responsibilities concentrate in the designated leader. section 1.2.1
  • ScyllaDB instead distributes ownership and replicates rows across nodes. section 1.2.1

How ScyllaDB in Action covers it

How deep it goes
Defines leader responsibilities and failover, then contrasts decentralized routing without detailing leader-election algorithms.
Examples
Uses node failure, replacement-leader election, and ScyllaDB request routing as concrete contrasts.
What you can do after
Evaluate whether centralized leader coordination fits a distributed database’s availability and fault-tolerance needs.
How it connects
Connects leader election with distributed systems, replication, fault tolerance, and consistency.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of ScyllaDB in Action. The section links point to the parts of the book it draws on.