Intro to PostgreSQL Caching layers: App vs. Proxy vs. Database

/u/compy3 Reddit r/webdev 2026-09-12 23:32 25 views

I haven't seen too many comprehensive approaches to this topic, so I took a swing at it.

Goal isn't to be exhaustive, but to be thorough enough to help people trying to get their bearings on the topic.

It covers the core differences and trade-offs of different cache flavors:

In your application layer
At the proxy level
In the database

Did I miss anything?

Edit: I'm curious what everyone's actual production stack looks like for this. I dropped my mental model on the cost vs. complexity trade-offs in the comments below. Wondering if people actually handle read optimization that way.

submitted by /u/compy3
[link] [留言]

Read original: https://www.reddit.com/r/webdev/comments/1wefn9k/intro_to_postgresql_caching_layers_app_vs_proxy/

My Favorites →

← Previous How can one easily create a search bar for specific words on a website? Next → I let an AI make phone calls, then took the word "booked" away from it

Postgres RLS in Symfony: three green isolation tests, and the UPDATE that moves tenant 1's invoices into tenant 2's books

Two articles ago I wrote that the Postgres role which runs your migrations bypasses every row-level security policy. Last week I wrote that with one tenant in the fixture, your isolation suite passes with no policy at all. Both came out of the same comment thread, and by the end of it we had three a

Database 09-14 35 Dev.to (EN Zone)

Turning Mermaid ER diagrams into shareable 3D schema tours

Turning Mermaid ER diagrams into shareable 3D schema tours Mermaid erDiagram is great for docs and PRs. It’s less great when the schema gets dense: boxes overlap, FK lines tangle, and “just zoom out” stops helping. I built Schema3D for that moment: open a Mermaid ER (or SQL / DrawDB) in the brows

Database 09-14 30 DEV Community

finally understand why redis blocks on one slow command, wish I knew this earlier

been learning redis properly for a side project and putting together notes as I go so I actually remember this stuff. always just knew "redis is in memory so it's fast" and left it at that. turns out the part that actually matters is that it runs commands on a single thread. that's not a downside, i

Database 09-14 27 Reddit r/webdev

Tracing Which Internal Consumer Read Each Webhook Event (One Registration, One Queue)

Use one webhook registration, land the payload in a durable queue, and make every internal consumer acknowledge its own copy. That is the least complex design that survives a downstream outage and still answers the question an auditor asks six weeks later: which internal service read which event, un

Database 09-14 30 DEV Community

Comments0

No comments yet — be the first