Last time we took a look at SQL, one of the most popular declarative APIs, and imagined what it would look like if identifiers were controlled by the system instead of the user, e.g. you must look up the identifier for a table in order to add records to it.
This was inconvenient, but workable within the sequential context of SQL execution. Now, let's use a less contrived example to see how it extends to control plane APIs, where forcing sequential execution makes modeling workflows complex and frankly just not fun.