technologybriefs
10:18in productionCh. 1 · Ingres’ successor/ 10:18 · ceiling 15 min
Software · Systems

PostgreSQL

University of California Berkeley · 1996

PostgreSQL isn’t open-source by accident—it’s the deliberate, decades-long rejection of SQL as a marketing veneer.

PostgreSQL is a free and open-source RDBMS that solves the problem of building reliable, scalable, and standards-compliant relational data systems without vendor lock-in. It emerged from Berkeley’s POSTGRES project in 1985 to address limitations in contemporary databases, especially Ingres’ lack of SQL support and type extensibility.

SoftwareSystemsComputingOpen sourceProgrammingComputing across the network →
Chapters & takeaways4
  1. 0:58
    Ingres’ successor

    PostgreSQL began as POSTGRES in 1985 at UC Berkeley to fix what Ingres missed—especially SQL support and extensibility.

  2. 2:37
    The SQL promise

    The 1996 rename to PostgreSQL marked a hard pivot: SQL was no longer optional—it was the core contract.

  3. 4:30
    Engine-only discipline

    It delivers ACID, views, triggers, and foreign keys—but only the engine. Nothing else is in scope.

  4. 6:00
    No platform, just portability

    It runs everywhere—from laptops to data lakes—but assumes you’ll build your own tooling, orchestration, and observability.

Worth your time?

Yes. Study the whole thing.

4.5/ 5
What works
  • ACID transactions
  • SQL:2023 Core compliance
  • cross-platform portability
  • type and function extensibility
What does not
  • solve database-as-a-service abstraction
  • provide client-side tooling
  • include operational automation
Study it if
  • developers who need strict SQL compliance
  • teams requiring ACID guarantees across distributed workloads
  • organisations rejecting proprietary licensing models
Skip it if
  • teams expecting built-in cloud management
  • non-technical stakeholders needing zero-configuration deployment
  • projects relying on vendor-backed ecosystem tooling
The written brief1 min read

What it is and the problem it solves

PostgreSQL is a free and open-source RDBMS that solves the problem of building reliable, scalable, and standards-compliant relational data systems without vendor lock-in. It emerged from Berkeley’s POSTGRES project in 1985 to address limitations in contemporary databases, especially Ingres’ lack of SQL support and type extensibility.

How it works

PostgreSQL implements ACID transactions, automatically updatable views, materialized views, triggers, foreign keys, and stored procedures. It runs on Windows, Linux, macOS, FreeBSD, and OpenBSD. Its engine handles workloads from single machines to data warehouses, data lakes, or high-concurrency web services.

What works

ACID transactions work. SQL compliance works—conforming to SQL:2023 Core. Cross-platform support works—Windows, Linux, macOS, FreeBSD, OpenBSD. Extensibility works—via custom types, functions, operators, and procedural languages.

What does not

It does not solve database-as-a-service abstraction, client-side tooling, or operational automation. The PostgreSQL Global Development Group builds only the engine and closely related components—not drivers, ORMs, dashboards, or managed offerings.

What it changes

It establishes that a relational database can be both rigorously standards-compliant (SQL:2023 Core) and open-source without corporate stewardship. It proves extensibility and correctness need not be traded for convenience.

Is it worth your time

Yes—if you need a mature, extensible, SQL-compliant RDBMS with strong consistency guarantees and no licensing cost. Its development is narrowly focused on the engine itself, not tooling or cloud abstractions.

Same field · Software4 of 102
10:03
Go (programming language)Robert Griesemer, Rob Pike, Ken Thompson · 2009Go is a statically typed, compiled programming language designed in 2007 by Robert Griesemer, Rob Pike, and Ken Thompson at Google to improve programming productivity for multicore, networked machines and large codebases. It combines static typing and runtime efficiency like C, readability and usability like Python, and high-performance networking and multiprocessing. Publicly announced in November 2009 and released as version 1.0 in March 2012, Go emphasizes simplicity, safety, and developer tooling — especially around concurrency via goroutines and channels, packaging, testing, and deployment — while deliberately omitting features like inheritance, assertions, pointer arithmetic, and implicit type conversions. Its design reflects a focus on the software development process itself rather than just language syntax or semantics.
9:44
Apache CassandraFacebook · 2008Cassandra is a distributed, wide-column database built for write-heavy, multi-datacentre workloads. It prioritises availability and scalability over consistency. It requires upfront schema design aligned to access patterns. It was developed at Facebook for inbox search and released open-source in July 2008.
10:00
Apache HadoopYahoo · 2006Hadoop is not a database or a query engine. It is a fault-tolerant batch-processing substrate built for scale, not speed or simplicity.
10:34
Amiga 10001985The Amiga 1000 is not defined by what it promised, but by what it delivered on day one: a working, shipped, ROM-locked implementation of preemptive multitasking — alongside deliberate physical design choices that treated the case as functional infrastructure. Its limitations are architectural, not aspirational.
Up next in Technology

PowerBook

· 9:20

It didn’t invent the laptop—but it invented how you hold one.

Play nextBack to Software
9:20