EEMBD
Loading…
Loading…
The delivery agent. Lands the data where the work becomes visible, and makes re-runs safe.
Theo loads harmonized, validated data into the destination and publishes it, to a marketplace, a warehouse or an application. A pluggable strategy registry handles different targets, so the same agent delivers to very different destinations.
He binds the data to the destination's identity, generates a load plan, and runs an FK-safe, idempotent upsert, so re-running a pipeline never duplicates or corrupts. After loading he verifies entity counts and referential integrity before confirming the work is publishable.
Eve's validated entities.
Loaded, published data at the destination, verified and idempotent.
Select the strategy and generate the load config.
Open the loader change for review.
Run the load against the destination.
Verify counts and referential integrity.
Publish to the consumer marketplace or app.
“The destination is where the customer sees the work.”