Configure AWS Advanced JDBC Wrapper connection pooling with the assistant

This article explains how to configure connection pooling for the AWS Advanced JDBC Wrapper on Amazon Aurora and Amazon RDS, comparing external and internal pooling approaches.

• AWS Advanced JDBC Wrapper uses a plugin-based architecture that intercepts JDBC calls to add Aurora and RDS capabilities without replacing the community driver
• External pooling (above the wrapper) pools logical connections and is framework-friendly but has limitations with read/write splitting
• Internal pooling (inside the wrapper) pools physical connections per instance, enabling topology-aware benefits like efficient read/write switching and leastConnections load balancing
• Enable internal pooling via connectionPoolType parameter (HikariCP or c3p0) or custom HikariPooledConnectionProvider for fine-grained control
• JDBC-WRAPPER-CONFIGURATION-ASSISTANT is an AI tool that helps choose pooling settings through Greenfield, Review, or direct configuration modes
• External pooling suits simple single-endpoint apps without read/write splitting; internal pooling excels with read/write splitting and reader load balancing
• Key differences include pool location, topology awareness, configuration approach, and failover/read-only switching behavior

Choosing between external and internal pooling depends on workload patterns, topology, security requirements, and operational standards; the JDBC-WRAPPER-CONFIGURATION-ASSISTANT can guide configuration decisions.