Importing master data
This section details the process of importing your master data, such as stores and menus, to Future Ordering.
Orchestration system
Importing and processing of data is managed by an internal orchestration system. This system routes data through a sequential series of jobs, allowing multiple sources to contribute to the final imported entities. An integrating system can, depending on its specific use cases and requirements, insert themselves anywhere in this chain.
The orchestration system is built around the following core concepts:
Jobs
A job is a single step in data import flow. Each job contains an HTTP endpoint that you provide to Future Ordering. When the import runs and it's time for your job, Future Ordering calls your endpoint and you perform whatever your job requires — fetching data from a source system, transforming it, enriching it, or similar.
Run your job asynchronously and report progress as work completes, so administrators can monitor the import.
Flows
A flow is a collection of jobs that together import a selected data type. It defines the steps (jobs) and the order in which they run.
Runs
A run is a single execution of a flow. It moves through each step in sequence and either completes or fails based on what each job reports. Future Ordering calls each job and waits for it to report completed or failed before continuing to the next.
Example - a step by step data import:
- A run is triggered for a flow that imports stores.
- Future Ordering calls the first job in the flow with any relevant configuration.
- Your endpoint reports back that it has accepted the job.
- You process the required data, upload it, and report back once complete.
- Future Ordering passes your data to the next job in the flow.
- Once all jobs finish, the run is complete.