Do you need separate systems when you already have Postgres? (postgresisenough.dev) | HN Screenshots

YHacker Newsscreenshots

Screenshot of postgresisenough.dev: Do you need separate systems when you already have Postgres?

First screen, captured 3 months ago.

Looks similar

Screenshot of gist.github.com: PostgreSQL is enough (2024)

PostgreSQL is enough (2024)(gist.github.com)

94 points by Imustaskforhelp 4 months ago | 64 comments

Screenshot of gist.github.com: PostgreSQL is enough

PostgreSQL is enough (gist.github.com)

314 points by cpursley 2 years ago | 219 comments

Screenshot of database.dev: Dbdev – A database package manager for PostgreSQL trusted language extensions

Dbdev – A database package manager for PostgreSQL trusted language extensions (database.dev)

138 points by samwillis 3 years ago | 50 comments

Screenshot of pglite.dev: PGlite – Embeddable Postgres

PGlite – Embeddable Postgres (pglite.dev)

535 points by dsego 10 months ago | 105 comments

Homepage of PGlite, an embeddable Postgres build that runs a full database locally in WASM with reactivity and live sync.

pglite postgresql webassembly electricsql

Screenshot of raphaelbauer.com: PostgreSQL for Everything

PostgreSQL for Everything (raphaelbauer.com)

412 points by karlmush 2 months ago | 238 comments

A blog post by Raphael Bauer arguing for using PostgreSQL as the single backend for many workloads instead of specialized tools.

postgresql databases software-architecture

Screenshot of supabase.com: Supabase Vector, the Open Source Vector Toolkit for Postgres

Supabase Vector, the Open Source Vector Toolkit for Postgres (supabase.com)

55 points by samwillis 3 years ago | 7 comments