In a highly scalable NoSQL system, which concept is typically prioritized over strict consistency?

• A. ACID
• B. BASE: Basically Available, Soft state, Eventual consistency
• C. Normalization
• D. Strong consistency with immediate consensus

Answer: (B)

In highly scalable NoSQL systems, the priority is to stay available and tolerate partitions, even if data isn’t perfectly up-to-date at every moment. This mindset is captured by BASE: Basically Available, Soft state, Eventual consistency. Basically Available means the system responds to requests even if some nodes fail; Soft state indicates that the stored data can change over time as replicas update; Eventual consistency means that, given enough time without new updates, all copies will converge to the same value. To achieve huge scale, these systems avoid heavy, global coordination that enforces strict, immediate consistency, accepting temporary inconsistencies for the sake of speed and availability. This stands in contrast to ACID, which emphasizes strict consistency and transactional integrity typical of traditional relational databases. Normalization is about reducing data redundancy and isn’t the guiding factor for NoSQL scalability.