Which statement best describes the difference between ACID and BASE in MIPC contexts?

• A. ACID guarantees atomicity, consistency, isolation, and durability (typical for RDBMS).
• B. BASE guarantees strong consistency and immediate replication across nodes.
• C. BASE (Basically Available, Soft state, Eventual consistency) is used in highly scalable NoSQL systems where availability and partition tolerance are prioritized over strict consistency.
• D. Both ACID and BASE require strict global consistency and immediate availability.

Answer: (C)

The main idea is the trade-off in distributed systems between strong consistency and high availability. ACID describes systems that enforce strict transactional guarantees—atomicity, consistency, isolation, and durability—so once a transaction commits, the data is consistently updated across the system. BASE, on the other hand, is used in highly scalable NoSQL environments where staying available and tolerant of network partitions is prioritized over immediate, strict consistency. It embraces a soft state and eventual consistency, meaning updates may propagate over time and replicas may be temporarily out of sync, but the system remains responsive.

This is why the statement about BASE being used in scalable NoSQL systems where availability and partition tolerance are prioritized over strict consistency is the best fit. The other options describe ACID, or incorrectly claim that BASE guarantees strong consistency or immediate replication, or that both approaches require strict global consistency and immediate availability, which BASE does not.