A Webinar by Tsahi Levent-Levi (BlogGeek.me) and Amir Zmora about WebRTC infrastructure. The option to build your own infrastructure, use an API platform or use SaaS services for some of the functionalities such as signaling, FW/NAT or media services.
6. So, You Want to Build an RTC Service?
1. What is WebRTC?
And more importantly – what’s missing in it (aka challenges)
2. Build vs Buy
Why should you choose one over the other?
3. Development alternatives
Get acquainted with the strategies
6
7. What is WebRTC?
And more importantly – what’s missing in it (aka challenges)
7
1
8. 8
WebRTC offers real time communication
natively from a web browser
WebRTC is a media engine with JavaScript
APIs
13. Many things missing
Client Side
• Browser support
• Mobile support
Server Side
• Interoperability with legacy VoIP deployments
• Signaling protocol
• Backend components
13
14. TheAnatomy of a VoIP Solution
14
Infrastructure
Signaling
Media Processing
Codecs
Source:
26. DevelopmentAlternatives
26
Level of dependency on 3rd parties
Level of
required
experience
in VoIP&
WebRTC
Self
Development
Integration
of Open
Source
Frameworks Integration
of Commercial
SDKs &
Frameworks
Employing
SaaS
Working
with an
API Platform
27. Frameworks
27
Framework Pedigree
SimpleWebRTC Web Technically sound, can be
easily used and extended
PeerJS Web Data channel related,
simple, lightweight
easyRTC Projects company Known in the market
31. Recommendations
1. Define your team’s core capabilities
2. Define MVP and future features
3. Decide on the weights of your KPIs
4. Search for platforms that fit our requirements
5. Try them out
31
33. Need more?
• What is WebRTC?
• What are the challenges in developing with
WebRTC?
• What are the available options to WebRTC
development?
• What are the KPIs when selecting an API platform for
WebRTC?
• What API platforms are there and how do they fit your
needs?
33
http://bloggeek.me/choosing-webrtc-api-platform/
Poll 1:
In what cases would you choose to use an API platform?
Always, no sense in building this
When video communication is not a core feature of my service
I would use it as long as I can white label the platform
Will not use it, no sense in vendor lock-in
At this point Amir will talk with Tsahi about the vendor lock-in, risks, alternatives. This will lead into the second part.
Amir will ask about the media services.
Are media and signaling services for conferencing, transcoding and recording compatible allowing for interchange? Can I for example use some SDK for client side and SaaS signaling, media handling and connectivity?
Amir will ask.
You have looked into the APIs of many of these platforms as part of your study for the report. Can you give some estimate how much time it would take to integrate a multi-party video call feature into a service, say a bank or insurance application.
If a company decides to switch API platform provider do you think that requires a redesign of the code or can code be built in a way to kind of be ready for that with different wrappers?
Poll 2:
What development alternative best fits your need?
Self develop from grounds up
Build using open source & commercial components
Build using SaaS components for infrastructure
API platform, focus on application only