HyperDB
HyperDB is an advanced database class that supports replication, failover, load balancing, and partitioning.
4.1(14 reviews)
·10 active installs·Updated 3 years agoAs of April 2026, HyperDB is a WordPress mysql plugin with 10 active installations and a 4.1/5 rating from 14 reviews. It has been downloaded 187K+ times in total. Requires WordPress 4.2+ and PHP false+. Available on WordPress.org since 2016. Last updated 3 years ago — may have compatibility concerns. Top alternative: Database Backup for WordPress.
4.1/514 reviews
10active installs
187K+total downloads
10 yearssince 2016
Overview
HyperDB is a very advanced database class that replaces a few of the WordPress built-in database functions. The main differences are:
* HyperDB can be connect to an arbitrary number of database servers,
* HyperDB inspects each query to determine the appropriate database.
It supports:
- Read and write servers (replication)
- Configurable priority for reading and writing
- Local and remote datacenters
- Private and public networks
- Different tables on different databases/hosts
- Smart post-write master reads
- Failover for downed host
- Advanced statistics for profiling
- WordPress Multisite
It is based on the code currently used in production on WordPress.com with many MySQL servers spanning multiple datacenters.
Ratings & Reviews
4.114 reviews
5 ★
11
4 ★
0
3 ★
0
2 ★
0
1 ★
3
Compatibility
| WordPress | 4.2+ requiredTested up to 6.0.11 |
| PHP | false+ required |
Top Alternatives to HyperDB
Frequently Asked Questions
Changelog
1.9
- Restore the behavior where we retry failed connection attempts to masters;
- Unbreak the logic for marking servers as down – in r2625068 the key for marking server as down was mistakenly changed to “server_readonly_$host$port” instead of “server_state_$host$port”
- If all masters are marked as read-only, ignore the read-only flag and still try to connect; otherwise we might end up incorrectly breaking the master connections for 2 minutes (APCu cache time) if we had temporarily set read-only on them;
- Fix a bug where having $dbhname in the server state keys can delay marking server as down or read_only by doing it once for all possible datasets and operations instead of once for the host+port;
- Fix a bug where we could mark server as read-only even though the ER_OPTION_PREVENTS_STATEMENT error was returned for a different reason; now we match to make sure we actually have ‘read-only’ in the returned error;
…and 7 more changes
Contributors
Plugin data sourced from WordPress.org. Analysis and metrics by PluginSift.