For years, we’ve built elaborate scaffolding around our databases message queues to broadcast changes, cron jobs to sync schemas, webhooks to notify downstream systems. We needed this scaffolding because Postgres was “just” a database, a place to store rows and run queries. The r...

Neon offers BM25 full text search directly within Postgres, via ParadeDB’s pg_search extension. You can read more about that in our announcement post, and in our comparison with Elasticsearch and with tsvector/tsquery in Postgres. The TL;DR is that supporting flexible full text s...

When we started working on app.build, we knew in the longer run we wanted to build a generic agent that could build apps with different “coding stacks”. However, for our first release and initial announcement, we could only build apps written with a single fixed stack React + Vit...

“We replaced both Pinecone and RDS with Neon, and latency dropped from 200ms to 80ms with a much simpler setup. Neon also gave us a smoother developer experience across multiple regions. It just works” (Giorgi Kenchadze, Founder & CEO at Vecstore) Vectstore is a new AI search pla...

Neon’s storage architecture is designed for scalability, but scalability alone doesn’t guarantee performance. Over the past several months, we’ve been focused on making the Neon storage system faster – cutting down ingest latency, reducing read amplification, making better use of...

“Timing is everything.” Some say that’s a quote from Shakespeare, but imho, the true bards of time are the 52 contributors to the pg_cron extension. The concept being pg_cron is simple run scheduled jobs directly within Postgres using familiar cron syntax. The simplicity belies t...

Modern OLTP database systems such as Neon and AWS Aurora separate storage and compute. The main benefits of this architecture are elasticity and being “serverless”. Storage appears “bottomless” and compute scales up and down with the load. A user doesn’t need to commit to a certa...