12/8/2025 at 8:29:47 AM
by ingve
12/12/2025 at 12:43:27 AM
It's funny how "push vs pull" always sounds like a technical choice, yet it usually exposes the social wiring of a team more than anything else. When every system expects to be pulled from, you start to see who actually depends on whom, and where the real bottlenecks live. The post captures that quiet truth that architecture isn't just code, it's how people negotiate responsibility.by idk_edwin
12/11/2025 at 11:07:35 PM
The biggest driver for push vs pull in my experience is “who does the work”. If I need data and I have to ask 7 different teams to “push”, it ain’t happening.by darth_avocado
12/12/2025 at 1:08:12 AM
So… caches. The unfortunate reality of high used systems.by cognomano
12/12/2025 at 9:43:53 AM
Or indexes, which are after all a structured way of duplicating data for performance, sometimes so much so that they entirely replace the actual table row lookup.by cwillu
12/12/2025 at 9:46:25 AM
Yepp, making exactly that same point in the post:> This is why we have indexes in databases, which, if you squint a little, are just another kind of materialized view, at least in their covering form.
by gunnarmorling
12/12/2025 at 2:50:30 AM
Yeah that was a lot of words to say caching is needed sometimes.As always it's an engineering decision full of tradeoffs. You should never duplicate your data, except when you need to...etc etc.
by samdoesnothing
12/12/2025 at 12:08:39 AM
dupe of: https://news.ycombinator.com/item?id=46184366by tedyoung
12/12/2025 at 12:17:37 AM
... and don't forget to flush!by mawadev