Skip to main content
Select Page

Announcing eXtremeDB/rt 2.1! Advanced flash simulation, smaller footprint and embedded connectivity.
Learn more

Reliable In-Memory Database System

Proven the fastest and most reliable in-memory or hybrid database system from edge to cloud.

eXtremeDB was designed specifically as an in-memory database system, not an afterthought.

Why does this matter?

When a database management system is created, it will, by design and implementation, be either an in-memory database system or an on-disk database management system. This initial choice affects the fundamental optimization strategies that will be baked into the database system code.

To optimize an on-disk database is to minimize disk I/O, so its design will use extra CPU cycles and extra memory to reduce or eliminate I/O. Conversely, IMDSs by definition eliminate all disk I/O. In other words, their optimization is primarily about delivering the highest performance at a given level of processing power. For an in-memory database, the focus is on reducing demand for CPU cycles. Because memory is storage for an IMDS, reducing memory overhead (i.e. RAM consumed for anything other than storing data) is also a key objective.

For a more in-depth explanation about why this matters, please review the McObject research paper, “Will The Real In-memory Database Please Stand Up” on this specific topic.

How does this help developers? 

Using eXtremeDB on embedded platforms (e.g. ARM, PowerPC, eXtremeDB is platform independent,) typical write accesses are at the level of a few microseconds, or less, and read-only access is sub-microsecond. When used on workstation or server platforms, performance is sub-microsecond. Learn more by reading “In-memory vs. RAM-Disk Databases: A Linux-based Benchmark“.

When eXtremeDB is used as an embedded database system, the engine is reentrant, allowing for concurrent access by multiple execution tasks or threads. Used on multi-tasking platforms (e.g. Linux and VxWorks RTP), databases can be created in shared memory for concurrent access among many processes. eXtremeDB transactions support the ACID properties, assuring data integrity.

eXtremeDB can also operate as a client/server database system. Client applications can be local (executing on the same system as the eXtremeDB server) or remote (executing on different systems that are connected to the eXtremeDB server system via TCP/IP). Systems can be heterogenous, e.g. a server on PowerPC and remote client on x86.

Incremental backup and restore
^

“Real vs. imitation in-memory database systems” – what’s the difference and why does it matter?

^

Why is the IMDS an ideal way to reduce memory consumption in embedded systems?

^

eXtremeDB runs on the device, gateway and server, leveraging staff skills to cut development time.

^

eXtremeDB is the only embedded IMDS to offer an integrated incremental backup feature (opens in a new tab) that detects changes at runtime. This unique, lightweight, high-efficiency mechanism is designed to support the performance and reliability needs of in-memory database applications.

^

“Real vs. imitation in-memory database systems” – what’s the difference and why does it matter?

^

Why is the IMDS an ideal way to reduce memory consumption in embedded systems?

^

eXtremeDB runs on the device, gateway and server, leveraging staff skills to cut development time.

^

eXtremeDB is the only embedded IMDS to offer an integrated incremental backup feature (opens in a new tab) that detects changes at runtime. This unique, lightweight, high-efficiency mechanism is designed to support the performance and reliability needs of in-memory database applications.

Incremental backup and restore

Faster hybrid data storage

Unlike other IMDS, eXtremeDB can combine the strengths of on-disk and in-memory database systems. In other words, eXtremeDB databases can be all-in-memory, all-persistent, or have a mix of in-memory and persistent tables. This unparalleled flexibility enables developers to tailor data management in order to optimize applications for speed and persistence. System developers can make intelligent trade-offs between performance, cost-efficiency, power consumption, and physical space-conserving data storage hardware.

^

eXtremeDB enables the developer to easily combine both database paradigms – in-memory and on-disk – in a single database instance.

^

Learn why being designed and implemented as an in-memory database system is a crucial first step for a hybrid database system.

^

Learn how eXtremeDB reduces memory consumption.

^

eXtremeDB is the only embedded IMDS to offer an integrated incremental backup feature (opens in a new tab) that detects changes at runtime. This unique, lightweight, high-efficiency mechanism is designed to support the performance and reliability needs of in-memory database applications.

eXtremeDB hybrid storage diagram

Related resources

Incremental backup and restore
^

Read more about in-memory database performance in the research paper, Gaining an Extreme Performance Advantage, examining on-disk database system performance vs. that of an IMDS operating with transaction logging.

^

11 Myths About In-Memory Database Systems. (opens in a new tab)” In-memory database systems have become popular and commonplace in the 2000s. Nevertheless, misinformation and misunderstandings still abound about the technology. This article in Electronic Design (opens in a new tab)will attempt to set the record straight.

eXtremeDB FAQs

More features

Documentation

Get a free trial