Live Streaming Challenges & How we are Dealing with Them

Presentation about the different live streaming workflows we have at CBS Interactive and how we're trying to create an inclusive, cost-effective and rock solid live streaming platform to be used by all the business units of the company.

1. LIVE STREAMING CHALLENGES & HOW WE ARE DEALING WITH THEM Flavio Ribeiro, 2018
3. REQUIREMENTS
4. • multiple live events per week • pretty high quality • interactivity • low-latency • low/medium audience peaks • syndication
5. • multiple ad-hoc concurrent events • large variety of inputs • low quality • low audience
6. • all-access • live linear channels • affiliates (monetization, ads)
7. • “internet breaking” event • record breaking audience • multiple revenue models • multiple backup plans • multiple devices
9. PROBLEMS • fragmentation on current implementations • vendors granularity (and the impact of it in contracts) • independent initiatives • development cost ↑ • Infrastructure maintenance ↑ • different integration with other platforms • CMS, live-to-vod, clips, thumbnails • too expensive for some BU's
11. • centralize live stream workflows for “ad-hoc” and live-linear channels • enable all users to benefit from new features • provide abstraction layer for cloud interfacing • reduce vendor lock-in • transparent switch between vendors • enable smaller business units to do live streaming events • easier/cost-effective
13. POST /channel
14. Response
16. GET /channel/097c3605h9
17. Response
18. payload parsing & processing media ingest plugin media origin plugin media edge
19. payload parsing & processing media ingest plugin media origin plugin media edge “input”: { “type”: “RTP”, } , “output”: { “dvr”: true, “protocols”: [“dash”] } AWS MediaLive AWS MediaPackage
20. payload parsing & processing media ingest plugin media origin plugin media edge “input”: { “type”: “RTMP”, } , “output”: { “protocols”: [“lhls”] } NGINX-rtmp + Lua
21. media edge
22. • CDN setup & configuration management • general purpose • all sorts of content (JS, images, static pages)
23. POST /endpoint CDN 1 CDN 2 CDN 3
24. CDN 1 CDN 2 CDN 3
25. CDN 1 CDN 2 CDN 3
26. CDN 1 CDN 2 CDN 3
27. payload parsing & processing media ingest plugin media origin plugin media edge
28. payload parsing & processing media ingest plugin media origin plugin
29. STATUS
30. FUTURE • support syndication
31. FUTURE • support syndication • finalize stand-alone CMS
32. FUTURE • support syndication • finalize stand-alone CMS • open source
33. thanks! @flavioribeiro