Rate Limiting

KalamDB applies rate limiting at SQL, auth, WebSocket, and per-IP connection layers.

Key Settings

Practical Starting Point

[rate_limit]
max_queries_per_sec = 100
max_messages_per_sec = 50
max_subscriptions_per_user = 10
max_auth_requests_per_ip_per_sec = 20
max_connections_per_ip = 100
max_requests_per_ip_per_sec = 200
request_body_limit_bytes = 10485760
ban_duration_seconds = 300
enable_connection_protection = true
cache_max_entries = 100000
cache_ttl_seconds = 600

Environment Strategy

• development: permissive but enabled (so behavior stays realistic)
• staging: mirror production values
• production: strict thresholds + alerts on violations

Tuning Workflow

1. collect baseline traffic per endpoint and user role
2. set limits just above normal peaks
3. alert on near-limit and over-limit events
4. adjust independently for auth, SQL, and WebSocket traffic

Signals To Monitor

• spikes in 429 responses
• repeated bans for same source ranges
• auth endpoint bursts
• large WebSocket fan-out patterns with rising rejection counts