# Overview The leader waits until a follower has confirmed that it received the write before reporting success to the client, and before making the write visible to other clients. # Key Considerations It is impractical for all followers to be synchronous a node outage could cause the system to come to a halt. # Pros - Enable strong [[Consistency]] between leaders and followers as the follower is guaranteed to have an up-to-date copy of the data that is consistent with the leader - Stronger [[Durability]] as we can be sure that the data is still available on the follower if the leader crashes # Cons - Introduces potential blocks in writes, which may impact performance # Use Cases # Related Topics