The Importance of Consistency in a Distributed Database

With a distributed database, you always write to one of the nodes. And there are different rules about is there only one leader that can take rights or can any node take rights? Can you only read from the leader? Can you read from any node? But no matter what database you're using, you always read or write to some nodes and then they replicate rights to other nodes. There's always a lag because that replication takes time. Making your code more complex, harder to work with. Now your code needs to be able to handle this situation. If you are aborted due to deadlock, should you retry that transaction or not? That's now something that the developer needs to make