What about OS Choices and Stacks?
The initial implementation was built using Windows, as it made use of several Windows-only third party tools, such as Windows and Flash Media encoders. Once it was live, we found that almost all of the operational challenges we faced arose from these third party tools. Over time id3as developed its own end-to- end suite of technologies (id3as.media) capable of replacing all these third party tools (apart from codecs) and doing so in a platform-agnostic way. This has allowed us to greatly improve platform stability and significantly reduce IaaS costs by moving from Windows to Linux, which is considerably cheaper by the hour.
How Is the System Controlled?
Agents in a NASDAQ OMX Corporate Solutions operations center based in Manila, The Philippines, and Leipzig, Germany, supervise the entire system, although there are disaster recovery capabilities across the world, since the management layer is entirely web based. Schedules for events are delivered by the NASDAQ OMX Corporate Solutions management systems into a resilient and distributed (cloud-based) database. These management systems are in multiple availability zones, and they receive instructions about when to fire up encoders for various events. Notification is presented on the web GUI to the supervisors.
This same web GUI allows the operator full control over the events, including cutting and editing on-the-fly (using DVR-like techniques to mark up the edit decision list) to ultimately produce on-demand files within moments of the live event finishing. The GUI also alerts the operator to any signal confidence failures and enables a single operator to supervise multiple events at the same time, greatly increasing the productiveness of the call center team. The id3as.media management and control subsystem is all written in Erlang, a language designed specifically to produce very large-scale, extremely available/ reliable distributed systems.