Preparing your workspaceloading the brief, studio & editor…

Loadingone moment…

extracttransformloadorchestrate

Scenario

6.Parceltrackingpipeline

SwiftShip packs customer orders in warehouses and ships them to the door. Every parcel is scanned at each stop — picked, packed, shipped, out for delivery, delivered. Those scans are taken on handheld terminals and drivers’ phones: devices that lose signal in basements, tunnels and rural rounds, and upload whatever they are holding when they reconnect. So a scan can arrive hours after it happened, and after scans that happened later. Design the pipeline behind the tracking page and the delivery-time reports.

This pipeline must answer

01Where is every parcel right now — when the scan that says so arrived four hours late?
02A “delivered” scan arrives before the “out for delivery” scan. What does the tracking page show?
03How long did each leg actually take — and does that number change tomorrow?

Guardrails

A customer refreshing the tracking page must never see a parcel go backwards
Ops read the delivery-time report each morning and it has to be right
A scan that arrives three days late must still reach both
Include a check before anything a customer or an analyst reads, and a path for scans you cannot read at all
Avoid invalid cycles

Act 1 · Specify — answer all 8 and your spec flows0 / 8 answered

1Trigger & cadence

Scans arrive whenever a device reconnects. The delivery reports are read each morning. So what runs, and when?

There are two deadlines in that sentence, and they are nothing like each other.

This choice changes which questions you are asked next — and the pipeline you end up drawing.

◆ What you are committing to on the canvas

How long can a customer wait to see a scan?
e.g.
They refresh the page while standing at the window. A scan that landed a minute ago should already be on it — nothing scheduled will do.
- configTrigger `Runs` = daily / hourly — leaving it unset is what fails the freshness check
Does the delivery-time report need the same speed?
e.g.
It is read once each morning, and it has to be right rather than early. That half can wait until the day is closed.
- nodeOrchestration & contracts → Scheduler trigger for a clock; Amazon MWAA, Step Functions, Dagster or Prefect when one step has to wait for another to finish

New to this?Batch vs Streaming vs Micro-batch

Edit your answer here✓ captured

Markdown: **bold** · *italic* · # heading · - bullet

Act 2 · Architect

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

40%

Design review

The reviewer reads your pipeline.

Run the review to check your architecture against this scenario — a valid DAG, a trigger for the freshness SLA, a transform stage, a quality gate before publish, and a failure path — then defend it in a short interview.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Preparing your workspaceloading the brief, studio & editor…

extracttransformloadorchestrate

Scenario

6.Parceltrackingpipeline

This pipeline must answer

01Where is every parcel right now — when the scan that says so arrived four hours late?
02A “delivered” scan arrives before the “out for delivery” scan. What does the tracking page show?
03How long did each leg actually take — and does that number change tomorrow?

Guardrails

A customer refreshing the tracking page must never see a parcel go backwards
Ops read the delivery-time report each morning and it has to be right
A scan that arrives three days late must still reach both
Include a check before anything a customer or an analyst reads, and a path for scans you cannot read at all
Avoid invalid cycles

Act 1 · Specify — answer all 8 and your spec flows0 / 8 answered

1Trigger & cadence

Scans arrive whenever a device reconnects. The delivery reports are read each morning. So what runs, and when?

There are two deadlines in that sentence, and they are nothing like each other.

This choice changes which questions you are asked next — and the pipeline you end up drawing.

◆ What you are committing to on the canvas

How long can a customer wait to see a scan?
e.g.
They refresh the page while standing at the window. A scan that landed a minute ago should already be on it — nothing scheduled will do.
- configTrigger `Runs` = daily / hourly — leaving it unset is what fails the freshness check
Does the delivery-time report need the same speed?
e.g.
It is read once each morning, and it has to be right rather than early. That half can wait until the day is closed.
- nodeOrchestration & contracts → Scheduler trigger for a clock; Amazon MWAA, Step Functions, Dagster or Prefect when one step has to wait for another to finish

New to this?Batch vs Streaming vs Micro-batch

Edit your answer here✓ captured

Markdown: **bold** · *italic* · # heading · - bullet

Act 2 · Architect

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

40%

Design review

The reviewer reads your pipeline.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Parcel tracking pipeline · Pipeline Builder scenario · D8LooP