McObject Offers Transaction Logging in eXtremeDB 2.3 Database
6/15/2004 - McObject® has released version 2.3 of eXtremeDBTM, its in-memory embedded database system, to final beta testing. The principal new feature in this release is an option to write database changes into a transaction log on persistent media, combining the performance and efficiency benefits of an in-memory database with the persistence of a conventional disk-based database.
eXtremeDB provides critical data management features—including transactions, concurrent access, and a high-level data definition language—while maintaining a tiny (as little as 50K code size) footprint for resource-constrained embedded systems. As an in-memory database, eXtremeDB delivers the real-time responsiveness demanded by consumer electronics, network infrastructure gear, industrial controllers and other intelligent devices.
In version 2.3, McObject 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. In the event of a hardware or software failure, the eXtremeDB runtime can recover the database using the log.
In keeping with its design principles, eXtremeDB 2.3 equips developers with the flexibility they need to tune transaction logging for their applications, including:
- 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. To provide the greatest developer flexibility, McObject provides a rich array of transaction logging control parameters, including depth of the recovery tree and maximum transaction log file size
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 logging’s impact on database writes, write performance far exceeds traditional disk-based databases in all cases (logging for eXtremeDB requires 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).
Developers interested in eXtremeDB Transaction Logging can download the documentation or browse http://www.mcobject.com/logging.shtml where they can also follow a link to enroll as a beta tester.
McObject provides complete source code for eXtremeDB. The database runs on popular embedded system platforms including VxWorks, QNX Neutrino, LynxOS and other RTOSs, and virtually all other operating systems, including Linux and Windows Embedded.
About McObject
Founded by embedded database and real-time systems experts, McObject offers proven data management technology that makes intelligent devices smarter, more reliable and more cost-effective to develop and maintain. McObject counts among its customers industry leaders such as DaimlerChrysler, Tyco Thermal Controls, Genesis Microchip, Motorola and Boeing. McObject, based in Issaquah, WA, is committed to providing innovative technology and first rate services to customers and partners. The company can be reached at +1-425-831-5964, or visit www.mcobject.com.
McObject and eXtremeDB are trademarks of McObject LLC.
Previous Page | News by Category | News Search
If you found this page useful, bookmark and share it on:
If you are familiar with RSS feeds, you can also sign up for our free blog feed. Our RSS feed is updated in real-time while our newsletter is updated daily.
