what is the context ? it seems to overlap with what we've been working on for the next electric

also keep in mind the naive solution should be quite efficient for reasonably low fanout, the entire downstream graph is touched but thanks to work-skipping optimization the previous states are reused

this is too automatically refresh oauth tokens

which for now are stored during the lifecycle of the application in an atom like {:token {:email .., :refresh-token .., :expiry ..}}

so I was looking to use (m/?> ##Inf ) to start m/sleep until expiry at which point the token should be refreshed

what about a map of atoms ?

that can work

as a quick interim solution

down the road this data will likely go into a datalevin at which point a tx-listener will provide granular updates that can be grouped by the eid

so the global atom is replaced by the database ?

yes in the future

that makes sense

then the db does the diffing

already doing this here https://github.com/lumberdev/tesserae/blob/master/src/tesserae/eval.clj#L437-L497

however, an example of diffing with missionary would be great. However, happy to use the map of atoms or db approach in the interim

but in this case you already have the diff information, that seems wasteful to re-diff the full map whenever it changes

it is the same complexity as having N watchers

one thing you can do is to use group-by on the flow of writes, in discrete time