HyperDB « WordPress Codex

HyperDB is a replacement for the standard wpdb class which adds the ability to use multiple databases. HyperDB supports partition of data as well as replication.

Partitioning of Data

This involves moving different tables or different parts of the database into different databases, and normally on different servers. This allows you to scale an application by adding more database servers, so your data could be spread across several servers.

HyperDB allows you to specify which data resides on which servers.

Replication involves having one database server act as the master (the central copy of all data) and other servers act as slaves (each with a copy of the data). All the database writes must go to the master server, but database reads can be sent to slave servers, thus spreading the load amongst multiple servers.

HyperDB allows you to split database writes and reads and assign each to an array of servers.

HyperDB allows multiple servers to be configured and multiple routes to servers. If the first server can’t be accessed the second server is tried, if that’s down the third server, and so on. This allows for failover from internal nics to public nics to remote datacentres, etc.



DRBD® refers to block devices designed as a building block to form high availability (HA) clusters. This is done by mirroring a whole block device via an assigned network. DRBD can be understood as network based raid-1.

In the illustration above, the two orange boxes represent two servers that form an HA cluster. The boxes contain the usual components of a Linux™ kernel: file system, buffer cache, disk scheduler, disk drivers, TCP/IP stack and network interface card (NIC) driver. The black arrows illustrate the flow of data between these components.

The orange arrows show the flow of data, as DRBD mirrors the data of a high availably service from the active node of the HA cluster to the standby node of the HA cluster.