According to McObject, eXtremeDB provides critical data management features -- including transactions, concurrent access, and a high-level data definition language -- while maintaining a tiny footprint (as little as 50KB code size) for resource-constrained embedded systems. Additionally, as an in-memory database, eXtremeDB can deliver real-time responsiveness to Windows Embedded applications running within consumer electronics, network infrastructure gear, industrial controllers, and other intelligent devices.
Version 2.3, expands eXtremeDB's options for persistence with transaction logging, a process in which changes made to a database by transactions are recorded to a log as they occur, according to McObject. In the event of a hardware or software failure, the eXtremeDB runtime can recover the database using the log.
The company says that eXtremeDB 2.3 provides flexibility in "tuning" transaction logging to meet application requirements with features such as:
- Configurable transaction durability -- Logging may be set to different levels of "transaction durability", allowing system designers to make intelligent trade-offs between performance and risk of unrecoverable transactions;
- Deferred cleanup -- After a database image is captured on persistent media (a "checkpoint"), prior checkpoints and transaction logs are no longer needed. Removal can be synchronized with checkpoint completion, or delegated to a background task;
- Wide-ranging control parameters -- The package provides a "rich array" of transaction logging control parameters, including depth of the recovery tree and maximum transaction log file size.
McObject claims that transaction logging does not alter eXtremeDB's all-in-memory architecture, which gives a performance advantage over disk-based databases. Database read performance is unaffected by transaction logging and, while developers have control over the degree of the loggings impact on database writes, write performance far exceeds traditional disk-based databases in all cases. Logging for eXtremeDB is said to require only a single write to persistent media versus the many writes required by disk-based databases for data pages and index pages modified during the transaction, plus the transaction log itself.
Further information about eXtremeDB Transaction Logging, including a link to enroll as a beta tester, is available
here.
Related stories:
