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.
This a16z piece argues Databricks is quietly building the data infrastructure that agentic AI will need to run inside real companies, tracing its path from Spark to the lakehouse to Lakebase. It ties that infrastructure to a bigger claim: that front-line workers will regain decision-making power from the managerial hierarchy that dominated the 20th century.
- Databricks grew from Spark, an open-source engine Matei Zaharia wrote at Berkeley that kept data in memory and ran iterative workloads up to ten times faster than Hadoop.
- The "lakehouse" merged cheap data lake storage with warehouse reliability, and the company says its Lakehouse runs at a more than $1.5 billion revenue run-rate, growing over 100% year over year.
- Databricks bought Neon in 2025 to build Lakebase, which separates storage from compute and removes the pipelines between operational databases and analytics, a setup the author says agents will depend on.