BUILD WorkshopClickHouse Workshops

Instructor track

Room-level run of show, shared-resource checklist, and per-module facilitator notes.

Your computer
macOS terminal: Run workshop commands in Terminal using zsh or bash.

This track is the facilitator's companion to the Learner track. Every learner module has a matching notes page here with four sections: Timing, Talk track, Common failures, and Reset steps. Read this landing page first for the room-level picture.

The learner path supports macOS and Windows. Windows uses Ubuntu on WSL 2 with Docker Desktop integration. Ask everyone to choose their computer in the page header before the setup clinic, and keep Windows learners in the Ubuntu terminal after bootstrap.

The learner track also carries a Running this workshop self-paced page for people doing the workshop with no instructor; it sends them to these notes as their answer key (and to the module 07 fault answer key only as a last resort), so keep this track accurate for that audience too.

Run of show

The session is three hours. The table below is the starting allocation; tune it during the dry run and record the final numbers here.

ModuleLearner lessonBudgetNotes
00Setup25 minFire-and-wait steps (service create, docker compose up) start before the talk
01ClickHouse Cloud15 minFirst "wow" on query speed
02Base app5 minNothing to build; keep it short
03Managed Postgres CDC20 minEach learner creates a managed instance; keep a managed cloud fallback pool
04ClickHouse Agents10 minBeta tool; have a fallback question ready
05ClickStack15 minTelemetry needs time to accumulate before module 07
06AI SRE15 minMCP OAuth is the fragile moment; pre-stage config
07Break and fix20 minDirect payoff from 06; hard-stop management matters
08Chat and Langfuse15 minKeys already set in module 00; restart plus trace tour
09Wrap-up10 minVolunteers demo; reset any shared state

These budgets total about 2 hours 30 minutes of hands-on work; the remaining time in the three-hour session covers the opening, transitions between modules, and the finale demos.

Tune the timing during rehearsal

The budgets above are the starting allocation. Confirm each against the timed dry run, and set a hard-pivot time for the incident lab (module 07) so module 08 and the wrap-up are never squeezed.

Shared-resource checklist

Some fallback resources are shared across the whole room. Confirm each is provisioned and healthy before doors open:

  • Managed Postgres fallback pool — cloud-hosted instances only for attendees whose org cannot create one. The primary path is one ClickHouse-managed Postgres per learner.
  • Loaner ClickHouse Cloud services — a small pool for attendees whose trial fails. TODO: pool size and distribution method.
  • Runtime LLM key pool — spend-capped fallback keys for the in-app chat (module 08).
  • Projector and shared channel — for the finale demos.
  • Venue network — enough symmetric bandwidth, no captive portal, OAuth-friendly.
  • Mixed-platform rehearsal — one clean macOS run and one clean Windows/WSL 2 run, including Docker integration, MCP browser OAuth, preflight, and Module 07 branch resets.

Setup clinic

Doors open early for a staffed setup clinic. Anyone whose prework did not fully pass should arrive then. TODO: confirm the clinic start time and staffing.

Per-module notes

On this page