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

Nick Chapsas Is Right About Clean Architecture (Mostly)

Stop Joining Tables In Your “Modular” Monolith

Rachael Wright-Munn: Unboxing Devcontainers and Docker for Rubyists

Zig 2026: No-AI Policy, $670K Foundation, Left GitHub & Why Zig Isn’t 1.0 - Andrew Kelley Explains

Vertical Slice Architecture doesn't mean “Share Nothing”

How PostgreSQL Quietly Took Over

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

Read Replicas Are NOT CQRS (Stop Confusing This)

The Modular Monolith: Scale Without Microservices

Don’t Use Boolean Flags in Python, Use Policies Instead

Postgres can replace your entire stack...

Eventual Consistency: Good, Bad, and a HUGE Mistake

The Modular Monolith Trap: Why Your Boundaries are Wrong

99% of Developers Don't Get PostgreSQL

I was using Postgres wrong this whole time

Postgres is NOT A DATABASE.

Stop using Event-Driven Architecture for your CRUD apps

Nvidia: Not for humans anymore?

How BAD is Test Driven Development? | Standup #6

