Skip to content

Exercises — Week 4 — One worker vs crew

Do these after reading Week 4. The “done when” is the comparison. No Docker, no worker pool, no 500 RPS.

1. One worker

Implement one_worker(rows) -> dict for a CloudWave changelog (title, body, review_required). Count calls = 1.

Checks:

  • calls == 1
  • Elapsed time recorded (time.perf_counter)

2. Crew of three role functions

summarizedraftqa as three functions (or a Crew you do not have to kickoff()). Count calls.

Checks:

  • calls == 3
  • QA asserts risks is present (fail if the draft dropped it)

3. Table

Fill:

Measure One worker Crew
Calls
Elapsed
Risks present?
Keep this version?

Checks:

  • Both rows filled
  • The conclusion may be “keep the one worker” or “keep two functions from week 2”
  • No Kubernetes / Prometheus / Docker requirement

Predict before you run

Will the crew of three beat one worker on elapsed time, or only on “risks present”? Is calls == 3 a win?

Runnable command

python your_one_vs_crew.py

Time both with time.perf_counter. No Docker, no 500 RPS.

Expected observation

Table filled: calls, elapsed, risks present, keep-this-version. Conclusion may be “keep the one worker.”

Self-check

The “done when” is the comparison, not a worker pool. No Kubernetes.