PostgreSQL uses a process-per-connection architecture. Every time a backend application opens a new database connection, PostgreSQL forks a dedicated worker process, allocating dedicated memory buffers (like work_mem) and incurring OS kernel scheduling overhead. In modern cloud-native architectures—where hundreds of microservices, serverless functions, or Kubernetes pods dynamically scale—this model rapidly leads to connection saturation, high memory pressure, and severe CPU