Even if you had multiple leaders responsible for different partitions you&#x27;d still be (temporarily) unavailable if the leader died, so...while you have improved the system&#x27;s availability characteristics you haven&#x27;t changed the underlying fault model.<p>Also, keep in mind that not <i>everything</i> has to go through the leader. If your application is OK with stale reads you can read committed data from any follower, allowing you to be available (for some definition of available) while the master is down.<p>Also, IIRC most <i>practical</i> strongly-consistent systems aren&#x27;t egalitarian (I&#x27;d love to hear otherwise) and instead, rely on a leader.