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.

dupe of: https://news.ycombinator.com/item?id=46184366

... and don't forget to flush!

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.

So… caches. The unfortunate reality of high used systems.