Learner track
Eight modules from source baseline through a defended hybrid architecture and teardown.
Work in pairs. One person operates the MigrationRoom dashboard while the other reviews the design; swap roles after schema design. The agent accelerates discovery and implementation, but your pair owns correctness, architecture, and every performance claim.
Keep two repositories available throughout the workshop:
- WorkshopHouse provides these UI instructions, architecture references, and optional
facilitator audit tooling under
workshops/databricks_migrationroom_lab. - MigrationRoom provides the Databricks source, dashboard, migration runner, and the six action buttons.
Module sequence
- Enter the room
- Establish the source baseline
- Discover and design
- Migrate, validate, and rewrite
- Benchmark the baseline
- Query multiple catalogs
- Build the native hot path
- Defend and tear down
If a command or cloud call fails, use Troubleshooting. Do not turn a missing service into a claimed result: preserve the error, mark the step not executed, and use the instructor demonstration only for discussion.
UI-first rule
Drive the migration with the six dashboard step cards and chat pane. Keep the selected run ID, copy the conversation link, and take redacted screenshots of the required UI checkpoints. Do not substitute standalone Python collectors or SQL runners for a MigrationRoom step.
Never put tokens, passwords, authorization headers, signed URLs, or credential-bearing connection strings into chat or screenshots. The workshop passes on correctness and defensible reasoning, not a predetermined latency result.