A brief history
PostgreSQL traces to POSTGRES at UC Berkeley in the 1980s by Michael Stonebraker. Open-sourced in 1994, renamed PostgreSQL in 1996. Over 35 years of continuous active development.
Core strengths
- ACID compliance — atomic, consistent, isolated, durable transactions.
- MVCC — readers never block writers; writers never block readers.
- Rich types — JSONB, arrays, ranges, geometric, network address types.
- Extensibility — custom functions, types, operators, index methods.
- Built-in full-text search — no external engine needed for most use cases.
JSONB
JSONB stores JSON in binary, making it indexable and highly queryable. This gives document-store flexibility inside a transactional RDBMS, without sacrificing joins, foreign keys, or ACID.
Extensions
PostGIS adds geospatial. pgvector adds vector similarity search for AI. TimescaleDB optimises time-series. Citus enables horizontal sharding. Postgres is a platform, not merely a database.
Why Modern Systems Choose PostgreSQL
Modern architectures choose PostgreSQL for its proven reliability, rich JSONB indexing, extensibility, and native support for full-text and vector search, eliminating the operational complexity of running separate databases.
