What Is Serverless PostgreSQL?

What is Serverless Postgres? | Databricks Blog Skip to main content

Summary

Serverless PostgreSQL decouples compute and storage so each scales independently, eliminating manual provisioning and charging only for active usage rather than idle capacity.

Cold start latency, connection management and variable pricing make serverless Postgres a strong fit for bursty or unpredictable workloads — but a poor fit for always-on, latency-sensitive applications.

Lakebase architecture builds on serverless Postgres to unify transactional and analytical workloads on a single platform, reducing data duplication and simplifying access for AI and real-time applications.

Serverless PostgreSQL (Postgres) is a fully managed cloud database model that decouples compute and storage. This allows each to scale independently and automatically based on demand. Instead of managing database servers directly, applications interact with systems that automatically provision compute resources in response to workload and scale them down when idle. In traditional Postgres environments, by contrast, teams must size infrastructure in advance, estimate capacity requirements and manage scaling over time. This often results in overprovisioning, idle-cost waste and performance bottlenecks when demand exceeds available capacity. Serverless Postgres removes much of that overhead by: Eliminating server provisioning and infrastructure management Removing the need for manual capacity planning Charging only for active usage rather than idle compute

The term “serverless” can be misleading, as it does not mean applications run without servers or infrastructure. The underlying systems still exist, but they are abstracted away and fully managed by the cloud provider. Tasks like server setup, scaling and maintenance are largely invisible to users and do not need to be configured or maintained directly. Traditional vs. serverless PostgreSQL PostgreSQL architectures have evolved over time, moving from provisioned infrastructure models to more dynamic, cloud-native designs. Traditional Postgres deployments run fixed compute resources continuously regardless of workload. Scaling requires manual intervention or preconfigured thresholds, with always-on costs incurred even when a database is idle. Serverless Postgres introduced a different model. Compute resources provision on demand, scaling automatically with workload activity and scaling down to zero when not in use. Billing is based on actual consumption rather than reserved capacity. Serverless Postgres can also be used alongside serverless compute platforms such as Databricks SQL, allowing analytical queries to run independently while still accessing the same underlying data within a unified lakehouse architecture . This shift is enabled by architectural changes such as decoupled storage layers and on-demand compute orchestration, which allow resources to scale independently and respond dynamically to workload activity. The key differences include: Feature Traditional Postgres Serverless Postgres Provisioning Manual infrastructure setup Fully managed by provider Scaling Manual or preconfigured Automatic and on-demand Cost model Fixed or reserved capacity Usage-based billing Compute behavior Always running Spins up per request, scales to zero Operational overhead High (maintenance, tuning) Reduced (managed service)

The next evolution: lakebase architecture As database architectures evolve, a third model is emerging that builds on serverless Postgres while addressing its limitations. This approach is sometimes referred to as lakebase architecture. Serverless Postgres improves scalability and reduces operational overhead, but it typically remains separate from analytical systems. This separation often requires data movement, duplication or synchronization between operational databases and analytics platforms. Lakebase architectures are changing the way we think about data storage and processing. They combine the power of transactional databases with the flexibility of a lakehouse foundation, creating a single platform where both operational and analytical workloads can run together. This means that instead of having separate systems for different tasks, everything can be done on one shared data platform. The result is less duplicated data and a much simpler way of accessing and using data. By bringing everything together, lakebase architectures make it easier to manage and analyze data, which can lead to better decision-making and more efficient operations. How lakebase architecture works Lakebase architectures build on serverless Postgres patterns while introducing tighter integration with cloud storage and data platforms. Key components include: Decoupled compute and storage Compute is stateless and scales independently, while storage remains persistent and distributed. Ephemeral compute Compute resources spin up to process queries and scale down when idle, enabling elasticity without maintaining always-on infrastructure. Log-based storage systems Data changes are captured as a continuous log, which can be used to reconstruct database state and support features such as branching, recovery and time-based access. Object storage as the foundation Durable data is stored in cloud object storage, enabling scalability, durability and alignment with lakehouse architectures. Control plane and orchestration A control layer manages scaling, routing and lifecycle events, coordinating compute and storage dynamically.

Why this matters By combining transactional and analytical capabilities on a shared foundation, lakebase architectures can: Reduce or eliminate data duplication between systems Enable near real-time analytics on operational data Simplify data architecture by consolidating infrastructure Support emerging workloads, including AI applications that require both transactional and analytical access

This shift reflects a move from optimizing individual systems to unifying them within a single data architecture. How serverless Postgres architecture works Serverless Postgres is built on a cloud-native architecture that separates compute and storage into independent layers. This foundational design principle improves efficiency and flexibility by allowing each component to scale independently. A key feature of this architecture is scale-to-zero behavior. When no queries are running, the system automatically suspends compute resources. When a new query is issued, compute is...