Preparing your workspaceloading the brief, studio & editor…

Loadingone moment…

extracttransformloadorchestrate

Scenario

39.Tentimesthetraffic,fortwoweeks

A music service publishes everyone’s year in review on the same morning. Traffic reaches ten times normal within four minutes of the 09:00 launch and stays elevated for a fortnight, while the ordinary daily reporting still has to work. Design the pipeline that holds.

This pipeline must answer

01The campaign launches at 09:00 and traffic goes to ten times normal within four minutes. What absorbs it?
02You cannot add capacity fast enough. What falls behind, and who decided it would be that?
03Two weeks later the traffic drops back. What is left over, and what does it cost until somebody clears it?

Guardrails

Adding capacity takes eight to twelve minutes, and the load arrives in four
The traffic is not evenly spread — everybody opens the app at once, and phones that were offline upload weeks of listening as a single burst
Twelve million summaries, each seen once by the person it is about
Include a check before anything is published, and a failure path
Avoid invalid cycles

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

1Trigger & cadence

The campaign goes live at 09:00 on a known date and traffic reaches ten times normal within four minutes. What is running, and what starts?

A known date is a rare luxury. Say what you do with it.

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

◆ What you are committing to on the canvas

What is running continuously and what, if anything, is scheduled?
e.g.
Name each and say what it is responsible for. If both exist, say which one the campaign report depends on.
- configTrigger `Runs` = daily / hourly — leaving it unset is what fails the freshness check
You know the date in advance. What does that let you do that you could not do for an unexpected surge?
e.g.
Name one concrete action and when you would take it. “Scale up” is a category; give the thing you would actually change.
- 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

39.Tentimesthetraffic,fortwoweeks

This pipeline must answer

01The campaign launches at 09:00 and traffic goes to ten times normal within four minutes. What absorbs it?
02You cannot add capacity fast enough. What falls behind, and who decided it would be that?
03Two weeks later the traffic drops back. What is left over, and what does it cost until somebody clears it?

Guardrails

Adding capacity takes eight to twelve minutes, and the load arrives in four
The traffic is not evenly spread — everybody opens the app at once, and phones that were offline upload weeks of listening as a single burst
Twelve million summaries, each seen once by the person it is about
Include a check before anything is published, and a failure path
Avoid invalid cycles

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

1Trigger & cadence

The campaign goes live at 09:00 on a known date and traffic reaches ten times normal within four minutes. What is running, and what starts?

A known date is a rare luxury. Say what you do with it.

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

◆ What you are committing to on the canvas

What is running continuously and what, if anything, is scheduled?
e.g.
Name each and say what it is responsible for. If both exist, say which one the campaign report depends on.
- configTrigger `Runs` = daily / hourly — leaving it unset is what fails the freshness check
You know the date in advance. What does that let you do that you could not do for an unexpected surge?
e.g.
Name one concrete action and when you would take it. “Scale up” is a category; give the thing you would actually change.
- 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

Ten times the traffic, for two weeks · Pipeline Builder scenario · D8LooP