Hi Selim,
Thank you for answering, see my answers bellow,
1. When using the origin-edge-client design (like in the article), Can this support bidirectional stream/conversation, like the client who receives the stream from edge server, can also send his stream to other users?
Please correct me if I got it wrong. You want to use a system like torrent structure. Player also sending the received stream to another player. Am I right? We are supporting SFU topology. No not necessary like torrent like structure, perhaps what I want to know and understand is Antmedia scalability,
How do we scale AntMedia so that we can still use it like we are just accessing it like a single server, like
broadcasting/publishing using WebRTC or RTMP and viewed in WebRTC and/or RTMP as well, and ofcourse can support bidirectional as we are planning to make a conference type application (integrated to a game).
I read from another guy's question about doing an Antmedia clusters, but the Q&A stops and did not continued.
I found the articles on my original email thus triggered this chain, I am wondering if the articles above that uses a CDN like approach (origin-edge-client) can support bidirectional stream for us to build our Conference type application wherein palyer can broadcast streams and can also see other people like how zoom works.
2. Does using clusters in cloudformation supports bidirectional streaming as well?
When we support it, cloudformation can also support as well.
After I understand the request correctly, I can add a feature request for you.
I just asked this question because when i search for any topic with regards to Antmedia Scaling, Amazon's Cloudformation product always comes up, but all those articles and tutorials are all using HLS instead of WebRTC and is not clear whether it can support birectional stream like I described on our requirement above.
Hope everything is clear, ask me more questions if it is not :)
Thank you in advance