One important enhancement to eXtremeDB 3.0 is improved task scheduling, which employs a fast new synchronization mechanism that minimizes expensive context switches, while using fewer CPU cycles to resolve resource contention.

This results in improved performance and in greater scalability from low-end and even no-OS environments, to high-end Linux, Solaris, and HP-UX-based servers.

eXtremeDB 3.0’s NVRAM support presents a new recovery option for an in-memory database. NVRAM is memory that is backed up by a battery so even if a device is turned off or loses its power source, the content of the memory remains. eXtremeDB 3.0 enables a process to reconnect to the NVRAM-hosted database, initiate any needed cleanup, and then resume normal operation after the system reboots.

eXtremeDB HA version 3.0 adds support for “1-safe” or asynchronous replication. In 1-safe replication, a database transaction is committed on the primary node without waiting for updates to propagate to replica nodes, resulting in shorter resource holding time suitable for applications with less stringent reliability requirements.

eXtremeDB already supported 2-safe or synchronous replication for systems with the strictest durability requirements. The addition of 1-safe replication provides a new HA option for developers to tune availability and performance to the system requirements.

New features and enhancements have been added to the databases application programming interface (API), including support for direct structures, Classname deletion, and classname fieldname pack.

In previous versions, each individual field of data classes and structures were read/written individually. In eXtremeDB 3.0, an embedded structure can be declared 'direct' and interfaces will be created to read/write the entire structure.

Classname_delete_all() allows all objects of a class to be deleted in a single function call (previously it was necessary to delete objects one at a time). The result, again, is to eliminate repetitive coding, reduce footprint, and enhance performance.

Classname_fieldname_pack() is a new function to release memory tied up in "gaps" resulting from deleted elements in vectors. Memory is used more efficiently: more data can be stored in the same amount of space.

Version 3.0 also supports function classname_fieldname_pattern_search() pattern-matching, similar to the SQL wildcard capability, in eXtremeDB’s native API. Pattern-matching expands eXtremeDB’s partial-key search (e.g. all names starting with “Jo”) to more complex patterns that include wildcard characters, such as “Jo*n*, which would match “Jones,” “Johnston,” etc.

eXtremeDB 3.0’s new Database browser utility enables a user to browse and edit a database’s contents during development, for testing and verification.

eXtremeDB 3.0 can generate interface enabling programs to read from and write to eXtremeDB from different machines on a network. In earlier versions, programs interacting with the database had to reside on the same target system, or developers implemented their own remote interface, for example with SOAP or CORBA. Unicode.

eXtremeDB 3.0’s support for Unicode enables use of a wider range of character sets (such as many Asian alphabets), which simplifies the development process and adds to marketability of eXtremeDB-based products internationally.

McObject
Issaquah, WA,
+1-425-831-5964
www.mcobject.com