Periscope. According to an article from medium [1] Periscope had a peak of around half million daily broadcasts. This may mean that Periscope have handled many live broadcasts to tens of thousands of users simultaneously!<p>Here I can imagine some complex hybrid P2P and TURN server with regional load-balancing and limiting content exposed to users may do the trick for handling the traffic. But this will come with expensive cost.<p>So my question is, from point of view of a start-up which has a similar problem of scaling as traffic grows, how would you implement your handling of this traffic?<p>P.S I understand you may say start-up project with 10 live broadcasts would be a dream! So I will clarify, how do you gradually move so if the project is successful you can handle the traffic with minimized costs on bootstrap?<p>[1] https://medium.com/@somospostpc/how-many-periscope-broadcasts-are-made-daily-808ae7f32de#.w2tltjeul
My understanding is that companies with successful systems running at scale usually created those systems after throwing away a series of systems that ran at lower scale. In the case of video, Netflix threw away a system that sent DVD's through the snail mail.<p>The big problem is getting to the point where your problem is scaling. Scaling is a good problem to have.