Large conferences translates to media server, network, sometimes interop, and eventually session control requirements.
Ideally, media servers with excellent IP connections, distributed around the world, and behind GeoDNS.
It also often means some interop capabilities (signaling and/or media interworking), since many large conference use cases include some users on traditional video (SIP or H.323), Lync/Skype For Business and/or PSTN.
Finally, session control becomes important if we get into enterprise and service provider conferencing markets.
Those reqs - especially media intensive ones - are interesting in that they are mostly not Twilio's core competency. Do they build it? Partner for it? Do they care enough about those use cases?
The answers to those questions are very interesting given Twilio's tremendous developer ecosystem.
Ideally, media servers with excellent IP connections, distributed around the world, and behind GeoDNS.
It also often means some interop capabilities (signaling and/or media interworking), since many large conference use cases include some users on traditional video (SIP or H.323), Lync/Skype For Business and/or PSTN.
Finally, session control becomes important if we get into enterprise and service provider conferencing markets.
Those reqs - especially media intensive ones - are interesting in that they are mostly not Twilio's core competency. Do they build it? Partner for it? Do they care enough about those use cases?
The answers to those questions are very interesting given Twilio's tremendous developer ecosystem.