![nginx rtmp server nginx rtmp server](https://opensource.com/sites/default/files/uploads/stream-server_profilesetup.png)
The theory was fairly simple: it worked as stateful protocol on port 554 over TCP, and was a control layer on top of Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol (RTCP). In the old 90s days of POTS modems, RealNetworks pioneered the Real-time Streaming Protocol (RTSP: more: ) as a specialist alternative to HTTP then produced RealServer, which morphed into Helix Server ( (multimedia_project). How do we mutate to that from what we know about an HTTP web application?įirst, some streaming history. It's an arbitrary number as usually only 5% of your users are on simultaneously. Let's say we need to create 10,000 video streaming servers which can read static files from their origin (with unlimited bandwidth), but also host live services which record to disk. We all know how Peering ( ) and CDNs ( ) work. We all know the high-availability architecture for web applications using load balancers. To be honest, it's never been easy the problem has merely moved location: from the pipe, to the server farm. If you want to spin up a service like Netflix or Youtube, it's easier because of the technologies available, but it's tougher because of the scale. If it wasn't the client CPU speed and bad codecs, it was the ISP bandwidth, or the server capacity.
#Nginx rtmp server software#
It used to be hours of tedious work, combined with expensive proprietary licenses for single-server software desperately straining a CDN.