
MTAR T3D Sessions | When Postgres Is Enough | Replacing Valkey with PostgreSQL (Part 2)
In Part 2 of "When Postgres Is Enough", Michael Cooper and JD examine what it took for AgLedger to trust PostgreSQL with work previously split between PostgreSQL and Valkey.
Supporting two databases meant maintaining separate schemas, backups, restores, and state that had to stay coordinated. PostgreSQL did not need to outperform Valkey at every task. It only needed to handle AgLedger’s workload well enough to make the second system unnecessary.
Michael explains how pg-boss allowed him to move queue and rate-limiting work into PostgreSQL, and why managing connections became a more important constraint than memory. He also describes a three-hour test that subjected the system to multiple AI agents, interruptions, mutations, and adversarial attacks. PostgreSQL continued handling the workload without issue.
The conversation also covers RDS IOPS, long-running snapshots, database bloat, and vacuum behavior. Once Michael trusted PostgreSQL as more than a place to store data, he began moving more schema and record structure out of application code and into the database, reducing recompilation work and making customer deployments more flexible.
This episode explores the point where PostgreSQL stops being only the database and becomes the system coordinating the application around it.
Więcej odcinków z kanału "More than a refresh: Conversations with the most interesting people you've never met"



Nie przegap odcinka z kanału “More than a refresh: Conversations with the most interesting people you've never met”! Subskrybuj bezpłatnie w aplikacji GetPodcast.








