Platform Configuration for a Global Streaming Service
United States
Backend configuration and release engineering on an OTT platform serving live events at scale, across a four-environment deployment pipeline.
The situation
A streaming platform serving live events at global scale runs on configuration as much as code. Which features are active per market, how content is scheduled, what each device class may do — at scale the settings surface becomes its own engineering problem.
What we built
Configuration surface
New realm settings with their validation and propagation, deletion paths for settings that had never had one, and cleanup of device-specific configuration past its usefulness. A scheduled publish job for one device platform, running on Quartz.
Infrastructure
Account and permission management expressed as Terraform rather than console clicks, and deployment across four environments with regression coverage at each stage.
What mattered
A bad setting does not throw. It silently changes behaviour for whichever market it applies to, which makes the deletion path as important as the creation path — and it is routinely the one nobody built.
Outcome
Configuration work on a platform processing more than 25,000 live events and over $200M in transactions annually.