Durability

SingleStoreDB Cloud provides several options to control the trade-offs between performance and durability. In its most durable state, SingleStoreDB Cloud will not lose any transactions that have been acknowledged.

Transaction writes are replicated on two nodes before commit, to ensure updates are never lost in case of single-node failure thereby ensuring durability.

See CREATE DATABASE for more information.

Yes, you can configure the durability through the WITH {SYNC | ASYNC} DURABILITY option in the CREATE DATABASE and RESTORE DATABASE commands.

SingleStoreDB Cloud provides the “READ COMMITTED” isolation level. This guarantees that no transaction will read any uncommitted data from another transaction. Furthermore, once a change is observed in one transaction, it will be visible to all transactions.

Unlike the “REPEATABLE READ” or “SNAPSHOT” isolation level, “READ COMMITTED” isolation level does not guarantee that a row will remain the same for every read query in a given transaction. Applications that use SingleStoreDB Cloud should take this into account.

Even though regular transactions use “READ COMMITTED” isolation level, backups created using the BACKUP command use “SNAPSHOT” isolation level.

SingleStore is built on a cloud-native and highly resilient architecture that features high availability within the workspace. When cloud instances fail, SingleStore transparently handles the failures, replaces instances, and maintains workspace availability to the application.