The JusDB Database Engineering Blog

Configure Redis Cluster for horizontal scaling — hash slots, replication, failover, and client-side routing

Set up MySQL Orchestrator for automatic failover, topology discovery, and master election at scale

PostgreSQL WAL retention is a balancing act — too little and standbys fall behind; too much and you risk disk exhaustion. Here's how to configure wal_keep_size and manage replication slots safely.

Deploy Aurora Global Database for sub-second cross-region replication. Understand storage-level replication, planned failover vs unplanned, and write forwarding for read regions.

MySQL replication errors 1062 and 1032 stop your replica SQL thread silently. Learn to diagnose binlog failures, fix data drift with pt-table-sync, and configure GTID-safe replication.

Logical replication in PostgreSQL has a critical gap: slots do not survive failover. PostgreSQL 17 finally fixes this with failover slots, plus adds row and column filtering for selective replication.

MySQL Group Replication and Galera Cluster both promise multi-primary high availability, but they behave very differently under load, network partitions, and node failures.

MongoDB 8.0 brings significant replication improvements including faster elections, durable oplog writes, and changes to write concern behavior. Here's what changed and how to take advantage of it.

TiDB 8.0 is the most production-ready version of the distributed SQL database yet. With improved HTAP, stronger MySQL compatibility, and Resource Groups, it's compelling for teams outgrowing single-node MySQL.

PostgreSQL 17 is one of the most impactful releases in years. Incremental backups, vacuum improvements, logical replication failover slots, and planner enhancements are all production-critical changes.

TiDB uses Raft consensus protocol through TiKV to replicate every region across three or more nodes. Here's how leader election, log replication, and region management work in practice.

Use Apache Flink CDC to capture MySQL and PostgreSQL changes — stateful processing, exactly-once semantics, and Kubernetes deployment