I’m working on deploying a high available and scalable system with WOWZA. My system will deliver streams to clients via both live and vod (s3) applications. I have been reading a lot on the forums here, and found that the live repeater schema (origin/edge) along with WOWZA’s Dynamic Load Balancer seems that will work just fine. See below a great explanation by salvadore.
The solution I have then defined for my system is described in the picture below (sorry for the hand drawing):
This approach looks good but I see some problems, such as that the “origin/load balancer” server is the single point of failure in the system. In addition, and most importantly, I can’t think of any good way to load balance that specific server. Meaning what if the server is overloaded with many live encoders ? Configure a second “origin/load balancer” server seems that won’t work because the edges would be associated with first origin server. I have seen on this post a suggestion to put two servers in a DNS round robin, but the question is how would the edges know about the right origin (considering it has to match the live source)? Also there’s a note indicating that this may be achievable with some custom code. Any directions here would be appreciated.