Click any tag below to further narrow down your results
Links
Databricks, Snowflake, Google, Amazon, and Microsoft have all built AI-facing products on PostgreSQL, and this piece explains why the open license, extension model, and developer familiarity made it the shared choice. It also warns that "Postgres" now covers four different levels of compatibility, so buyers need to check which one they're getting.
- Databricks paid around $1 billion for Neon and Snowflake paid around $165 million for Crunchy Data, showing the premium the market puts on real Postgres compatibility plus modern architecture.
- Extensions like pgvector, pg_lake, and pg_duckdb turned Postgres into a single engine for state, vector retrieval, and analytics, which suits most AI workloads below very large scale.
- "Postgres compatible" ranges from the real engine to a wire protocol over a different database, and the extensions you rely on determine which layer you need and what leaving will cost.
Neon has launched Realtime in public beta, letting any SQL query stay live as the underlying data changes, with the sync running inside Postgres rather than in a separate service. The pitch is aimed at developers and coding agents who want reactive apps without polling or refetch logic.
- Any read-only, deterministic SQL query can be subscribed to, including joins, aggregates, and window functions, and the result updates as the data changes.
- Realtime runs inside Postgres, so there's no separate sync system to mirror or keep consistent with the database, and it's enabled per branch.
- It's free during the beta with no waitlist, and it's designed so it doesn't add load to the primary or keep a scale-to-zero database awake.