Enterprise-grade connection pool for HashiCorp Vault HTTP transport.

This module provides sophisticated connection pooling functionality optimized for high-throughput Vault operations. It manages connection lifecycle, health monitoring, load balancing, and automatic failover across multiple Vault instances in a cluster.

Enterprise Features

• Connection Pooling: Efficient HTTP connection reuse and management
• Health Monitoring: Continuous connection health checks and recovery
• Load Balancing: Intelligent request distribution across Vault nodes
• Connection Limits: Configurable pool sizing with overflow protection
• Timeout Management: Comprehensive timeout handling and recovery
• Performance Metrics: Detailed pool performance and health metrics
• Circuit Breaker: Automatic failover for unhealthy connections

Configuration

config :vaultx, :pool,
  size: 10,                     # Base pool size per Vault instance
  max_overflow: 5,              # Additional connections when pool is full
  timeout: 30_000,              # Connection timeout in milliseconds
  max_idle_time: 300_000,       # Maximum idle time before cleanup
  health_check_interval: 60_000 # Health check interval in milliseconds

Usage Examples

# Get a connection from the pool
{:ok, conn} = Vaultx.Transport.Pool.get_connection()

# Return connection to the pool
:ok = Vaultx.Transport.Pool.return_connection(conn)

# Execute request with automatic connection management
{:ok, response} = Vaultx.Transport.Pool.request(:get, "/v1/sys/health", nil, [])

# Get pool statistics
{:ok, stats} = Vaultx.Transport.Pool.stats()

References

• Connection Pooling Best Practices
• Vault High Availability

Pool Statistics

# Get pool statistics
stats = Vaultx.Transport.Pool.stats()
# Returns: %{
#   total_connections: 10,
#   active_connections: 3,
#   idle_connections: 7,
#   pending_requests: 0,
#   total_requests: 1234,
#   failed_requests: 5
# }

Health Monitoring

The pool automatically monitors connection health by:

• Sending periodic health check requests
• Removing connections that fail health checks
• Tracking connection error rates
• Implementing circuit breaker patterns for failing endpoints