Overview
These concepts apply to every SDK and every generator implementation.
Basic idea
When a Supplier starts, its Generators and Orchestrators register themselves with Sixpack. Sixpack uses that registered catalogue to route dataset requests to the right item.
Items are of two types:
- Generator - creates or provisions data in a target system
- Orchestrator - combines multiple Generators or other Orchestrators into a larger data-generation flow
Generators and Orchestrators are deployed together in a Supplier.
Catalogue structure
Sixpack uses a 3-level catalogue:
- Environment - target environment configured by the Supplier
- Supplier - deployed component that manages related Generators and Orchestrators
- Item - dataset type represented by one Generator or Orchestrator
Where to read next
- Task lifecycle and retries explains how Suppliers register, receive tasks, and handle state.
- Exception handling explains when to wait, retry, or fail a dataset.
- Run modes explains
DEVandDEPLOYMENT.