Consensus algorithms at scale: Part 8 - Closing thoughts

This post concludes a series on consensus algorithms by reconceptualizing key aspects: pluggable durability, revocation/establishment of leadership, handling races (favoring lock-based approaches for flexibility), and completing/propagating requests with versioning. It details how Vitess implements these concepts, specifically mentioning vtorc's plugin API for durability and the Vitess Operator for graceful failover, aiming for full auto-pilot operation. Future topics like failure detection, consistent reads, and node addition/removal are noted as separate concerns.