I Didn't Need Kubernetes, and You Probably Don't Either(benhouston3d.com)

308 points by bhouston 1 year ago | 300 comments

Zero-Downtime Deployments with Docker Compose(maxcountryman.com)

35 points by todsacerdoti 3 years ago | 0 comments

DKIM2 and DMARCbis Have Landed(stalw.art)

78 points by StalwartLabs 3 months ago | 58 comments

Setting Up an RK3588 SBC QEMU Hypervisor with ZFS on Debian(blog.kumio.org)

59 points by kumiokun 1 year ago | 17 comments

Kaizen #4: Overhauled Homelab(timharek.no)

23 points by meysamazad 3 months ago | 3 comments

LLM codegen go brrr – Parallelization with Git worktrees and tmux(skeptrune.com)

144 points by skeptrune 1 year ago | 66 comments

Unconventional PostgreSQL Optimizations(hakibenita.com)

398 points by haki 9 months ago | 63 comments

Blog post by Haki Benita presenting unconventional, creative techniques for speeding up queries in PostgreSQL beyond standard indexing and query rewrites.

Making Postgres slower(byteofdev.com)

320 points by AsyncBanana 1 year ago | 35 comments

A ByteofDev blog post humorously exploring how to tune PostgreSQL configuration settings to make the database as slow as possible.

Postgres recovery_prefetch can cause outages(ardentperf.com)

40 points by plaur782 4 days ago | 5 comments

Blog post by Jeremy Schneider explaining how Postgres recovery_prefetch amplifies replica IOPS and, with synchronous replication, can cause prolonged write outages, with a repro.

Building durable workflows on Postgres(dbos.dev)

329 points by KraftyOne 5 months ago | 137 comments

DBOS blog post by Peter Kraft arguing that Postgres alone is sufficient to build durable workflow execution, describing DBOS's architecture.

The startup's Postgres survival guide(hatchet.run)

474 points by abelanger 3 months ago | 206 comments

A Hatchet blog post offering startups a guide to keeping their Postgres databases from falling over under load.

Postgres LISTEN/NOTIFY does not scale(recall.ai)

547 points by davidgu 1 year ago | 283 comments

A Recall.ai engineering blog deep dive explaining why Postgres LISTEN/NOTIFY caused scaling problems in their production system.