Strong consistency is one of the common data consistency models in distributed database systems. Strong consistency guarantees that all writes to a single record will be applied in a specific order (sequentially), and writes will not be re-ordered or skipped. This means that writes that are acknowledged by the database as committed have been applied, and exist in the transaction timeline in contrast to other writes to the same record. This guarantee applies even in the face of network failures, outages, and partitions.

Some distributed database systems – including Aerospike – offer more than one consistency model. Strong consistency requires more processing and cluster resources, but Aerospike’s strong consistency data model has been optimized to provide maximum performance at scale.

Related Articles:

• BSV Association and Aerospike Achieve 100 Billion BSV Blockchain Transactions Per Day on Teranode

• The essentials of a modern distributed database

• Implementing strong consistency in distributed database systems