Explain the difference between strong consistency and eventual consistency.

Strong Consistency:

• All nodes see the same data simultaneously
• Reads always return the most recent write
• Updates are atomic across all nodes
• Higher latency due to synchronization overhead
• Example: Traditional RDBMS with ACID properties

Eventual Consistency:

• Nodes may temporarily have different data
• The system will eventually reach a consistent state
• Lower latency as updates can proceed without waiting for all nodes
• Better availability during network issues
• Example: DNS, Amazon DynamoDB, Cassandra

Key Difference:
Strong consistency prioritizes correctness over performance, while eventual consistency prioritizes availability and performance over immediate consistency.