core practice · system design prompt

Design exercise: Scheduling & Orchestration

Placement, queues, priorities, quotas, fairness, preemption, autoscaling, and reconciliation loops. Implement designOutline() returning non-empty values for: resourceModel, placementPolicy, fairness. Each value must name a concrete mechanism or decision.

The mechanism

Schedulers match constrained work to finite resources. Good orchestration separates desired state, placement policy, execution, observation, and correction.

Study Scheduling & Orchestration

Expected evidence

A design outline with resourceModel, placementPolicy, fairness plus an explicit failure mode or trade-off.

Try this drill in the practice workspace →

Hints when you need them
  • Name the failure mode before selecting the mechanism.

Check the sources

Browse all practice briefs