Maximizing Database System Reliability
Database system reliability encompasses protection from loss of database availability, safeguards on data integrity, and freedom from software defects/database corruption. These characteristics are built into eXtremeDB Financial Edition through several features.
ACID-compliant transactions. eXtremeDB Financial Edition’s transactions support the ACID (Atomic, Consistent, Isolated and Durable) properties, which safeguard data integrity by guaranteeing that interdependent operations either complete together or are cancelled together
Transaction logging. Optional transaction logging provides recoverability. While it might seem that transaction logging re-introduces on-disk storage overhead into in-memory databases, McObject’s benchmark tests confirm that an IMDS with transaction logging still outperforms a traditional “on-disk” DBMS performing the same tasks, even when the on-disk database is fully cached.
Non-volatile memory support. Using non-volatile memory as storage, in-memory databases gain durability while keeping high performance. (See McObject’s white paper, Database Persistence, Without the Performance Penalty.)
High Availability. eXtremeDB Financial Edition’s high availability option ensures continuous database operation even in the face of hardware or software failure. eXtremeDB Financial Edition’s HA support includes both synchronous (2-safe) and asynchronous (1-safe) replication, with application-directed failover.
Clustering. eXtremeDB Financial Edition’s clustering capability adds reliability via the presence of multiple, synchronized database nodes.
Advanced debugging and corruption prevention. The database runtime implements many verification traps and consistency checks. After application debugging, the optimized version of the eXtremeDB Financial Edition runtime can be used, removing traps and internal checks, and restoring valuable clock cycles. In addition, cyclic redundancy check is built into the backup-and-restore feature for in-memory databases, to ensure the database was written in its entirety when saved, and has not been corrupted.
eXtremeDB Financial Edition’s native C/C++ API is type-safe, so that any errors in data-typing are caught at compile time.