I'm Not Giving Up On Postgres as Cache (and neither is Microsoft)

Get the 2026 .NET Developer roadmap here → https://the-dotnet-weekly.ck.page/2026-roadmap
Want to master Clean Architecture? Go here: https://dub.sh/clean-architecture
Want to master Modular Monoliths? Go here: https://dub.sh/modular-monolith

In this video, I take a hands-on look at Microsoft’s new IDistributedCache implementation for PostgreSQL and put it to the test. No theory — just real code, real queries, and real benchmarks.

I walk through:
- How the new Postgres cache library works in .NET
- Wiring it up using IDistributedCache (just like Redis)
- Using unlogged tables vs write-ahead logging (WAL) and why it matters
- What actually happens inside Postgres (queries, expiration, cleanup)
- Performance benchmarks:
## Local vs remote database
## Reads vs writes
## WAL vs unlogged tables
-When Postgres as a cache makes sense
- And when Redis is still the better tool

This isn’t about replacing Redis everywhere. It’s about understanding the trade-offs and knowing when Postgres is “good enough” — especially if you already run it and want to avoid extra infrastructure.

If you’re building .NET APIs and already rely on PostgreSQL, this is an option worth understanding.

Check out my courses:
https://www.milanjovanovic.tech/courses

Read my Blog here:
https://www.milanjovanovic.tech/blog

Join my weekly .NET newsletter:
https://www.milanjovanovic.tech

Chapters

Видео I'm Not Giving Up On Postgres as Cache (and neither is Microsoft) канала Milan Jovanović