Context: In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency.

Question: What explains the difficulty in a system containing availability, consistency, and partition tolerance guarantees?
Answer: the CAP theorem

Question: How many guarantees will most databases tolerate?
Answer: two

Question: What is used to offer a balance in guarantees?
Answer: eventual consistency

Question: What can't explain the difficulty in a system containing availability, consistency, and partition tolerance guarantees?
Answer: Unanswerable

Question: How many guarantees will most databases destroy?
Answer: Unanswerable

Question: What can satisfy all guarantees at the same time?
Answer: Unanswerable

Question: What is used to discourage eventual consistency?
Answer: Unanswerable

Question: What has had low demand in recent years?
Answer: Unanswerable