🧠 Big mindset change for fast flow: don't PUSH synchronous changes through the system; instead, PULL changes asynchronously working backwards from outcomes.
@matthewskelton
(apologies if you already know this)
In protocols involving producers and consumers, we often talk about "applying backpressure" as a way to get the producers to back off so consumer aren't overwhelmed.
Seems to me that push works best if
consumers are generally overprovisioned
messages can safely be discarded
Of course, it doesn't work to allow a pull-based consumer to build up an ever-increasing queue of things to consume, but then responsibility shifts to producer.
@matthewskelton
I think maybe I jumped to conclusions then, that you were talking about on who's schedule task were committed to and executed. Sorry about that.
Would you care to elaborate? Particularly the "working backwards from outcomes" sounds interesting.
Add comment