Large streaming services have one particular characteristic: you almost can't just "rewrite" them properly. While developers change the architecture, the product keeps living – people watch shows, streams go live, new releases come out, marketing runs special projects. Everything has to keep working simultaneously.

Our work with mоre tv and CTC's platforms wasn't a "we built a cool new service from scratch" story. It was about a rather painful transition from a heavy legacy system to an architecture that could be properly maintained going forward.

The project had a lot of what typically accumulates over the years at large media platforms: a Rails monolith, tightly coupled services, shared databases, a large number of integrations, and infrastructure that was already difficult to change without risking breaking something.

Projects like this always highlight the gap between "ideal" architecture and real-world development. In theory, everyone loves rewriting from scratch. In practice, you're more often carefully disassembling a functioning airplane mid-flight: https://evrone.com/cases/ctc-moretv