Check out the paper "Dedalus: Datalog in Time and Space". It formalizes a Datalog to include time, specifically to handle async behavior. It explores exactly what you seem to be doing here.
Peter Alvaro gave a great presentation on Dedalus at Strange Loop 2015.
Have you read up on differential data flow? Might be what you want?
LOVE this. If anyone knows similar blogs that run through engineering decisions in real time, please share! Way more useful than a polished long post built for SEO and hackernews domination.
Substantively, I don’t have much to say other than building math into the core of innovative programs should be a more common practice than it is. Not necessarily as a part of the code, but rather the design, documentation, and sometimes even the user copy. Math has stood the test of time (200y +/- 10,000y) for good reason!
If you enjoy FRP-related stuff, Missionary[0] (in Clojure) is doing some really great work.
Most people discover it through Electric Clojure.[1]
The Missionary author has some really good talks he's done up on YouTube about it.
And someone built a spreadsheet with Electric Clojure
What are the YouTube talks? Did you have a specific one in mind?
Why are the resulting views in the future by exactly 1 time step?
This is RBAR by any other name.
HTTP requests, SQL queries is not async, for that matter not even sync.