-
Notifications
You must be signed in to change notification settings - Fork 84
LudicrousDB can route different tables or queries to different datasets, balance reads across replicas, prefer servers by topology, account for replica lag, and fall back between eligible connections.
Its dynamic callbacks can consult a persistent cache or another service to locate a table. Large installations can therefore maintain a mapping outside the application and change it without hard-coding every table in db-config.php.
No. It routes queries to existing databases. Provisioning, schema creation, data migration, replication, backups, and failover orchestration belong to your database and deployment tooling.
Configure replication in MySQL or your managed database platform, then tell LudicrousDB which servers may receive reads and writes. See Primary and Replica Databases and Replication Lag.
LudicrousDB randomly selects connections from the best available priority group. Lower positive read or write values are preferred over higher ones.
No. Both servers must already be synchronized and safe to write through database-native clustering or another tested failover design. A connection fallback is not leader election.
Dataset callbacks inspect the current query and $wpdb state, then return the logical dataset that owns the table. See Partitioning Recipes for examples and migration cautions.
No. LudicrousDB is a database drop-in, not a conventional plugin with an activation workflow. Install one code copy, add the drop-in files, and verify the active $wpdb class as described in Installation.
No performance advantage has been measured. LudicrousDB does retry connections and delays connecting until a query is needed, so a heavily cached site may remain partially available when its database is temporarily unreachable.
The query fails after eligible connections and retries are exhausted. Register a db_connection_error callback in db-config.php if the application should render a custom response or stop in a specific way.
See Support and Security before posting configuration or logs. Never include passwords, private keys, connection strings, or other credentials in a public issue or discussion.
LudicrousDB documentation · Repository · Support