@gunnarmorling There are multiple ways to handle reads, each with its own trade-off space. Many of the recent Paxos read optimizations apply to Caspaxos as well. But if a system handles reads as writes to avoid staleness, then yes - those reads inherit the same issues as writes
@gunnarmorling That said, some systems naturally have an organic single writer/reader per labeled register (e.g., a user working with their own data). In those cases, dueling isnโt really a concern for Caspaxos, especially if the system is modeled as a set of independent, rewritable registers
@gunnarmorling In general Iโm not a fan of broad generalizations :) but yeah, itโs nice when a system has a weak leader or a mostly single-writer pattern to guarantee liveness
Spent some time digging into the #CASPaxos paper ("Replicated State Machines without logs"), by @rystsov. It's really easy to follow; do I get it right though that two competing writers could block each other from ever moving beyond the prepare phase?
https://t.co/x4hjjkNvHi
@gunnarmorling So overall, I think weak-leader election should stay modular and not be bound to any specific replication protocol, as long as the protocol can support it
@gunnarmorling And during outages, it can make sense to let SREs override leader election entirely and pin a static leader to reduce variability and stabilize the cluster
@alenkacz When you know how to code, have full-stack experience, and have passions outside of programming, the opportunities are endless. I had an idea for an app, and with fewer responsibilities at the time, I decided to take a leap of faith
Surprising how wrestling with JavaScript years ago helped me onboard with modern C++ & Seastar (cooperative concurrency within core-pinned threads) to develop Redpanda, a distributed streaming platform