Load Plans
As we have seen so far, packages only handle serialized execution. Each step executes after the previous one and before the next. Load Plans will bring additional functionalities that will allow for more advanced orchestration of the processes.
Serial and parallel steps
When a Load Plan is defined, the first operation is to define if steps will be executed in sequence or in parallel. You can obviously mix and match serialized and parallel branches as needed.
In the previous example, we will load our Customer data and our Product data in parallel, since there is no dependency between these two sets. Each set can be made of several steps that can be, in turn, executed in a serialized or parallel fashion. You can see here that steps in each set are executed in sequence. When both sets are completed, we then process our Sales data. This step is serialized because it is dependent on both customer and product data.
Objects that can be used in a Load Plan
The following objects can be used...