MCOBJECT Partner's Website

eXtremeDB Transaction Logging v 8.0

eXtremeDB Transaction Logging provides recovery capabilities for McObject's in-memory embedded database in the event of device or system failure. When transaction logging is active and enabled, all updates to the data objects are logged to a set of files on disk, or on a network device. If the memory content is damaged or destroyed, the exact state of the database is restored by an automatic roll forward procedure.

With the eXtremeDB embedded database version 2.3, McObject increases the options for persistence with the introduction of transaction logging - a process that journals changes made to a database (by transactions), as they are made. With transaction logging enabled, the eXtremeDB runtime captures database changes and writes them to a file known as a transaction log. In the event of a hardware or software failure, the eXtremeDB runtime can recover the database using the log. Logging is performed through periodic checkpoints, where the image of the in-memory database is saved to persistent storage, and all intermediate changes to the database are written to the log files. In this way, the RAM database is made persistent.

Transaction logging does not alter the all-in-memory architecture of eXtremeDB, which retains a performance advantage over disk-based databases. Read performance is unaffected by transaction logging and write performance will far exceed write performance of traditional disk-based databases.

The reason is simple: eXtremeDB transaction logging requires exactly one write to the file system for one database transaction. A disk-based database, however, will perform many writes per transaction (data pages, index pages, transaction log, etc) and the larger the transaction and the more indexes that are modified, the more writes that are necessary.

To minimize the performance impact, eXtremeDB equips developers with all the controls they need to tune their applications with persistence and performance in mind. Many eXtremeDB transaction logging features are parameterized so that programmers can invoke the features most appropriate for their application scenario. For example, transaction logging may be turned on or off at runtime and, when turned on, logging may be set to different levels of transaction durability, allowing system designers to make intelligent trade offs between performance and risk for unrecoverable transactions.

• Partner Product Website

• Category Data Management & Analysis
• Highlights

  Rancher Catalog

  This icon indicates whether the software is included in the Rancher Catalog.

  Rancher Extension

  This icon indicates whether the software is a Rancher Extension.

  Cloud-Native Network Function

  This icon indicates whether the software possesses Cloud-Native Network Functionality

  High Availability

  This icon indicates whether the software provider has flagged the compatibility of the application with the SUSE High Availability extension. Success may include the application running in an HA environment, or it may include extensions to the application to exploit and integrate with the HA feature. Please see the software provider's web site for more details.

  Integrated System Available

  This icon indicates whether a pre-built, pre-configured integrated version of the application is available. This may also be called an appliance and may be packaged as a hardware appliance, a software appliance, or a virtual appliance.

  Virtualization Ready

  This icon indicates whether the software provider supports the application in any of the virtualized environments that work with SUSE Linux Enterprise. These may include one or more of Xen, KVM, VMWare, or other hosting environments. Also note that virtualization support can mean that the solution can be used in the cloud environment. Please see the software provider's web site for more details concerning which environment(s) are supported by the provider.