Heat currently uses a strategy of only creating/deleting/updating one resource per stack at a time. It does this in in dependency-topology order which keeps the code simple and guarantees things happen in the intended order. With large stacks, this will mean a significant amount of time spent waiting unnecessarily. We should discuss the problem space and various strategies to reduce waiting.