Help me choose:  Distributed Database Contrast & Compare

eXtremeDB for HPC delivers the benefits of distributed database management via distributed query processing, clustering and high availability options.

Distributed Query Processing

eXtremeDB for HPC partitions, or shards, a database and distributes query processing across multiple servers, CPUs and/or CPU cores. Performance is accelerated — dramatically, in some cases — via parallel execution of database operations and by harnessing the capabilities of many host computers rather than just one.

The benefits of distributed query processing are evident in McObjects recent STAC-M3 benchmarks.  We partnered with E8 Storage, IBM, and Lucera Financial Infrastructures to name a few.  In these tests, the eXtremeDB database was partitioned horizontally across up to 128 shards, resulting in record-setting performance managing tick data.  Please use the following link to review a summary of the benchmark records.

eXtremeDB offers different distributed database options to address different objectives.  Learn about Sharding with eXtremeDB, or review this table that lists different distributed database uses and options.

High Availability

High availability enables deployment of a master database and one or more synchronized replica databases. Replication is between separate hardware instances and features application-directed fail-over with strategies that include 2-safe (synchronous) and 1-safe (asynchronous). It delivers “five nines” (99.999% uptime) reliability, or better, with eXtremeDB for HPC’s unsurpassed performance. In addition, read-only replicas are available to support distribution/load-balancing of database query/analysis/reporting requirements.

Clustering

In clustered deployments, every eXtremeDB HPC database instance serves as a master. This means that changes to one node are efficiently replicated to others.  It is unique as the first clustering database system to offer an embedded architecture.  The database system runs within the application process at every node, eliminating the need for separate client and server modules.