Problems / Design a product, medium
Design GitHub Actions from an empty canvas: every push starts a pipeline on a shared runner fleet, with artifacts, logs and live status.
Unlock it once for 15 credits; everything inside it is free (runs, changes, Submit, results, hints). Sign in with Google to start; new accounts get free credits.
Request types to route: status (65%, read), logs (30%, read), webhook (5%, write). Budget: $4,200 a month.
You start from an empty canvas. When you run the tests, each one simulates your design with its own traffic and failures:
| Test | What it does | Passes when |
|---|---|---|
| Normal day | The normal day: the traffic in the brief, nothing broken. | Success ≥ 99.9%; p99 latency ≤ 200 ms (status); p99 latency ≤ 500 ms (webhook) |
| Monday-morning merge rush | At 5 s a team merges a stack of pull requests: traffic triples for 8 s, 150 new jobs a second. | Success ≥ 99%; p99 latency ≤ 800 ms (webhook) |
| A server dies | At 4 s one server of the first app service on the request path dies for 10 s. | Success ≥ 99% |
| Database 5× slower | At 5 s the main database on the request path answers 5× slower for 8 s. | Success ≥ 99%; p99 latency ≤ 500 ms (status) |
| Budget: $4,200/month | The normal day's design must cost at most $4,200 a month. | Cost ≤ $4,200/month |