Future objects are the simplest way to write these workloads because they map directly to a very simple 2-step model 1) I want this, get started 2) I'll check

Future objects are the simplest way to write these workloads because they map directly to a very simple 2-step model 1) I want this, get started 2) I'll check when I need this, then I'll wait This is what I do when I want to order pizza for pickup and it's easier to debug most of the time - they're only annoying when the pizzas ordered were never picked up (& you get a memory leak, eventually).