The JusDB Database Engineering Blog

Debezium 3.0 turns your database transaction log into a real-time event stream with full before/after row images. Learn to configure CDC for PostgreSQL WAL and MySQL binlog, avoid the offset storage trap, and monitor replication lag.

Use PostgreSQL CTEs and recursive queries for category trees, graph traversal, and complex aggregations. Covers MATERIALIZED vs NOT MATERIALIZED and cycle prevention.

Tune PostgreSQL 18 WAL and checkpoints without weakening crash safety: understand commit modes, measure checkpointer deltas, and validate archive recovery.

Implement database CI/CD with Flyway migrations, GitHub Actions pipelines, pytest schema tests, and blue-green deployment patterns. Eliminate ad-hoc schema changes.

A practical guide to hardening PostgreSQL: configure SSL/TLS, tighten pg_hba.conf, implement least-privilege roles, enable row-level security, and set up audit logging.

PostgreSQL's logging system is powerful but requires careful configuration to be useful in production. Learn how to capture slow queries, connection events, and DDL changes without drowning in noise.

Upgrade PostgreSQL major versions with sub-second downtime using logical replication. Step-by-step guide covering schema copy, subscription setup, lag monitoring, and sequence resync.

Build a complete database observability stack with Prometheus metrics, slow query logs, and OpenTelemetry distributed traces. Includes alert rules for replication lag and cache hit rate.

PostgreSQL 17 ships eager freezing and improved autovacuum prioritization, the most significant vacuum improvements in a decade. Learn how to tune autovacuum for high-write tables and prevent transaction ID wraparound.

Guide the PostgreSQL query planner with enable_xxx settings, pg_hint_plan extension, and extended statistics for correlated columns. Fix bad plans without rewriting queries.

Use pgbench to benchmark PostgreSQL before and after configuration changes. Covers scale factor selection, TPC-B and read-only workloads, custom SQL scripts, and latency percentiles.

Use pg_repack to reclaim PostgreSQL table bloat without the exclusive lock of VACUUM FULL. Covers installation, table vs index repack, disk space requirements, and throttling.