Database / ScyllaDB Interview questions
Explain the execution flow of a write request in ScyllaDB?
A write in ScyllaDB moves from client to coordinator to replicas, with durability and consistency handled at distinct points along the way.
The client sends the write to any node, which acts as coordinator for that request and computes which replicas own the relevant token range. It forwards the write to all of them in parallel; each replica durably appends it to its commit log and applies it to its in-memory memtable before acknowledging. The coordinator waits only for the number of acknowledgments required by the requested consistency level (e.g. a quorum) before telling the client the write succeeded - it doesn't need every replica to respond immediately, and any replica it couldn't reach gets a hint stored for later replay. This is why writes in ScyllaDB are fast even at high consistency levels: the expensive part (durable commit log append) is spread in parallel across replicas rather than serialized through a single leader.
More Related questions...