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.

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.

Webull! Receive free stock by signing up using the link: Webull signup.