Neon runs warm pools of compute and storage so new database creates are fast and generally don't require resource changes on AWS. This architecture meant we could still run 99.9%+ of database operations throughout the incident.

We’ve been using Devin by @cognition_labs to improve our docs. We’re using it to: – Tackle repetitive tasks like typo fixes and link cleanups – Polish UX copy and UI text – Go faster through our backlog t.co/grGpsTqTnK

In the last few months, we've been working on making Neon storage faster. Here are 7 improvements we shipped to boost performance under the hood 🧵

Twenty years of Postgres hacking! Tune in as Aaron Francis interviews Neon’s co-founder and Postgres core contributor, Heikki Linnakangas, about his work on Postgres, Neon's origin story, and what lies ahead. Watch here: t.co/ztnqi7T1R8

Separation of storage and compute ≠ slow reads from extra hops On Neon, the compute layer can use LFC (Local File Cache) to serve hot reads without a trip to storage layer.