SYSTEM Cited by 1 source

Netflix Connector Controller

The Connector Controller is Netflix's dynamic registry / control plane that determines which data-movement connector to use for a given job (Source: sources/2026-06-19-netflix-the-evolution-of-cassandra-data-movement-at-netflix).

How it works

1. A Maestro workflow executes a Decider step for each data-movement job.
2. The Decider step invokes the Connector Controller with the job's attributes (source cluster, table name, destination, migration cohort).
3. The Controller returns the appropriate connector: either Casspactor (legacy) or Move Data (new).
4. On Move Data failure, the Maestro workflow's conditional step immediately falls back to Casspactor — zero user impact.

Role in migration safety

The Controller gave the Netflix team instant, per-job routing control without modifying any downstream customer workflow. Upgrades and rollbacks for any data movement were a configuration change in the Controller.

This is the canonical wiki instance of the Decider Pattern for data-movement systems.

Seen in

• sources/2026-06-19-netflix-the-evolution-of-cassandra-data-movement-at-netflix — described as the registry backing the Decider Pattern for zero-impact migration.