Content tagged with "database"
Measured Blue/Green Switchover downtime through RDS Proxy with psql. Compared against direct connection (26s) and JDBC BG plugin (0s) to quantify RDS Proxy's effect and constraints.
Hands-on verification of the Aurora DSQL SQLx connector for Rust. Connection code drops from ~50 lines to one, and the OCC retry helper works — but default max_attempts=3 falls short under high concurrency.
Integrate the Remote Query Cache Plugin into a Spring Boot app with application.yml config and ApplicationRunner warmup. Verified with both node-based TLS and Serverless ElastiCache.
Confirmed 98.9% hit rate over 1 hour of continuous load. No timeout recurrence after 10-minute idle. Combined with AWS docs' connection reuse recommendation, Serverless + warmup is production-viable for sustained traffic.
Compared node-based+TLS to confirm the initial timeout is Serverless-specific. A warmup connection with a 5-second wait recovers CacheMonitor to healthy state, making Serverless viable for production.
Verified the Remote Query Cache Plugin in AWS Advanced JDBC Wrapper 3.3.0 with ElastiCache for Valkey Serverless. The first connection always times out, pushing CacheMonitor into SUSPECT state — a Serverless-specific issue not seen with node-based clusters.
Verified the Remote Query Cache Plugin in AWS Advanced JDBC Wrapper 3.3.0 with Aurora PostgreSQL (1M rows) and node-based ElastiCache for Valkey. A 749ms window function query dropped to 2ms. TTL-based consistency control worked as expected.
Upgraded AWS JDBC Wrapper from 2.6.4 to 3.2.0 and re-tested Blue/Green Switchover on both PostgreSQL and MySQL. MySQL's connection failure turned out to be timing-dependent (0–1 failures). Summarizes 3.x migration guidance.
Tested Blue/Green Switchover on Aurora MySQL and compared with PostgreSQL. IN_PROGRESS phase was only 3s (vs 12s for PG), but the BG plugin may have 0–1 connection errors (timing-dependent). HikariCP's stale writer problem is engine-agnostic. Plain JDBC stayed on old host for 31s after recovery.
Compared downtime during Blue/Green Switchover across Plain JDBC, HikariCP with retry, and AWS JDBC Driver BG plugin. The plugin recorded 0 failures in 400 queries during testing. HikariCP kept connecting to the old writer — a critical pitfall.
Measured real downtime during Aurora PostgreSQL failover vs Blue/Green Switchover. Failover had 12 connection failures in two separate windows, Blue/Green Switchover ~26s with 6 failures. DNS TTL of 60s is the key bottleneck.