The architecture and goal of oryx is clear. It will use a multiple-processes architecture, and each process handles some part of streaming process. For example, the shell is a manager, like the master process of nginx(not the same, just similar). The rtmplb(rtmp load balance) only proxy rtmp to backend processes(workers).
SRS2 is the best choice right now. Oryx supports working with SRS2 ok, by forking SRS2 processes and proxy http-flv and rtmp connection to SRS2. So I think oryx is better than it looks like.
I means we can use SRS2 as the streaming worker processes, and use oryx shell+rtmplb+httplb+apilb to work together with SRS2. In the future, the streaming worker for oryx will be rewriten in golang.
Big thanks to your teacher.
Based on your code name... It is just me randomly saying stuff
I'm practice my English and Mathematics, to read the latest researches. It's very hard to move up without more knowledge. I find most of the researches describing the problems by calculus...
For me as a computer engineer, you need American standard calculus II class before taking any further classes. So it is easy to understand why they use calculus so much.
@winlinvip Hello! I would like to contribute into your project. What do you think about it?
Please file PR to oryx.
As oryx consists of small programs, I think you can write a FLV edge program, which similar to RTMP edge to fetch stream from upstream. FLV edge should merge request, that is only one connection to fetch from upstream for multiple clients to play the same stream.
We have golang，php,vue,react,ios,android jobs, If anyone interested in , please contact me or send your cv to me, not remote job firstname.lastname@example.org
can anyone help me with this issue?
Hi! Is it possible to use SRS2 as HLS origin + edges cluster (to be compatible with apple devices)? Or RTMP origin + HLS edges? Everything will be ok, as long as the front is HLS and we'll be able to do clustering/load balancing.