PATTERN Cited by 1 source
Transparent migration¶
Execute a backend migration that is invisible to end users — including the ability to roll back per-tenant with a single operation.
Context¶
You're replacing platform internals but cannot afford user disruption or a big-bang cutover.
Solution¶
Design the migration as an operator-side toggle. Each tenant or customer can be enrolled in the new backend (or rolled back) independently, without any change to the user's submission flow or tooling. Combine with patterns/api-parity-migration to ensure the external contract is preserved.
At Netflix¶
Netflix operators migrated CMB tenants to Kueue by "clicking a button on a tenant in [their] UI." This toggle converts internal tenants to Kueue Cohorts and leaf tenants to ClusterQueue + LocalQueue. Rollback was equally simple — re-toggle the tenant back to CMB scheduling.
(Source: sources/2026-06-22-netflix-how-netflix-simplified-batch-compute-with-kueue)
Seen in¶
- sources/2026-06-22-netflix-how-netflix-simplified-batch-compute-with-kueue — per-tenant one-click migration and rollback between CMB and Kueue.