Appears on
Articles5
Scaling serverless Postgres: How we implement autoscaling
We’re excited to announce the release of autoscaling in Feature-Preview! This feature allows your database to accommodate varying workloads and meet your application’s demand. In this blog post, we’ll explore the concept of autoscaling and share the technical details of how we’ve...
1 Year of Autoscaling Postgres: How it’s going, and what’s next
Neon introduced autoscaling for serverless Postgres to the world over a year ago, enabling your applications to handle peak demand without incurring peak infrastructure costs 24/7. Our autoscaling feature performs zero-downtime vertical scaling of your Postgres instance, provisio...
Dynamically estimating and scaling Postgres’ working set size
With the announcement that Neon’s autoscaling feature is GA, we wanted to take the opportunity to dive into the implementation of a recent improvement we made: Scaling to match your workload’s working set size. This can provide extraordinary speed-ups for real-world workloads, bu...
Postmortem: Delayed Start Compute Operations
Summary On two occasions in the past week, Neon customers in AWS/us-east-1 were unable to create or start inactive databases, for a total period of 5.5 hours. Customers with running databases were unaffected. The root cause related to our ability to assign IP addresses to new dat...
AWS CNI lessons from a Production Outage
_This post is the last in a series discussing the Neon outages on 2025 05 16 and 2025 05 19 in our AWS us east 1 region. In this post, we cover the IP allocation failures that persisted through the majority of the disruption. For further details, read our_ top level Post Mortem h...