Interesting article, I wondered about this: It fetches function calls from DurableQs, consolidates them into FuncBuffers (ordered by importance, then execution

Interesting article, I wondered about this: It fetches function calls from DurableQs, consolidates them into FuncBuffers (ordered by importance, then execution deadline), Since that is a classic source of priority inversions (which is that 'important' messages overwhelm the system resulting in less important messages missing their execution deadline) If there is someone reading this that knows this system can you tell me if they queue ranking is actually rank = f(priority, deadline) ? Where things close to their deadline can out rank high priority things? The other question that I had but didn't get from skimming was how they do data management. Do the functions carry around all their data? Is any of that data part of a state machine? (which is to say mutating that data by the function results in a new 'state' which would affect other functions using that data)