The "Just Use Postgres" Trap
“Just use Postgres” is the modern architecture slogan. While simplifying your infrastructure sounds great, it doesn't always mean you've reduced complexity. Often, you’ve just relocated it. There is an "implementation tax" of using a relational database as a queue. While tools like Postgres, Kafka, and RabbitMQ might all store data, their semantics around retries, visibility timeouts, and concurrency are worlds apart. 🔗 Kurrent (formely EventStoreDB) https://kurrent.io 🔔 Subscribe: / @codeopinion 💥 Join this channel to get access to a private Discord Server and any source code in my videos. 🔥 Join via Patreon / codeopinion ✔️ Join via YouTube / @codeopinion 📝 Blog: https://codeopinion.com 👋 Twitter: / codeopinion ✨ LinkedIn: / dcomartin 📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo... 0:00 Intro 2:37 Behaviors 3:50 Implementation 5:57 Concerns

The Modular Monolith: Scale Without Microservices

Read Replicas Are NOT CQRS (Stop Confusing This)

Stop Using Rebase and Merge Like This (You're Doing It Wrong)

Postgres is slowly replacing every database

The 'Do-Not-Hire List' Is Real. Here's What Actually Gets You On It.

PostgreSQL queues done right with PgQ | POSETTE: An Event for Postgres 2026

Vertical Slice Architecture doesn't mean “Share Nothing”

Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker

Multi-Tenancy Isn't About Databases

The Postgres Performance Trap Every Developer Falls Into

Cerebras Killed Notion, Obsidian, and Your "Second Brain"

Stop Joining Tables In Your “Modular” Monolith

How PostgreSQL Quietly Took Over

How Instagram Scaled Postgres to 2 Billion Users

I was using Postgres wrong this whole time

Can you put a video in postgres?

You’re Building Modular Monoliths All Wrong

Postgres vs MySQL Transactions + Log-based writes (Database Internals Chapter 5)

Wait... PostgreSQL can do WHAT?

