Embed Size (px)
DESCRIPTION
These are the slides for the Upperside Webinar I talked at. The acquisition of AddLive by SnapChat created some discomfort among companies using a WebRTC API platform. It made the threat, well known to all those building their future on someone else’s service, apparent and real. If you are now planning your service the first decision to be made is whether to build your own infrastructure or use an API platform. Should decisions be made only in light of current happenings in the market? Are there more options except for to build or use a service? The selection of an API platform is an important one. There are over 20 such platforms available. But they are different. They don't offer the same set of capabilities, they aren't focused on the same types of use cases and customers. The selection process requires an understanding of the use case, the business values, the features and requirements you have. In this webinar, we will review the various KPIs and selection criteria, offering an instruction manual for vendor selection and self built infrastructure options.
Citation preview
To Build or Not to Build Your WebRTC Infrastructure
June 2014
Tsahi
Levent-Levi
Tsahi Levent-Levi
http://bloggeek.me
2
Amir Zmora
http://www.linkedin.com/in/zmora
Many factors to consider
3
Business Technical
Business Criteria
• Nature of your business
• Feature/Core
• Business model
4
Wikimedia
Technical Criteria
• Island
• Open/closed service
• Geographical distribution
• SLA requirements
5
pixabay
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
What is WebRTC? And more importantly – what’s missing in it (aka challenges)
7
1
8
WebRTC offers real time communication natively from a web browser WebRTC is a media engine with JavaScript APIs
How are Calls Made with WebRTC?
9
1
2
3 4
5
What does it provide?
• Real-time
• Voice, video and data
• Browser based
• No plugins
• Secured
• Interoperable (between browsers)
10
Why all the fuss?
11
12
So What’s
Missing?
Many things missing
Client Side
• Browser support
• Mobile support
Server Side
• Interoperability with legacy VoIP deployments
• Signaling protocol
• Backend components
13
The Anatomy of a VoIP Solution
14
Infrastructure
Signaling
Media Processing
Codecs
Source:
Boundaries of WebRTC
15
Infrastructure
Signaling
Media Processing
Codecs
Source:
An inherent tension
16
VoIP
RTC
WWW
Web
jasoneppink
Build vs Buy Why would you choose one over the other?
17
2
Requirements
• Voice or Video?
• Messaging?
• Multipoint?
• Mobile Devices?
• Recording?
• Storage?
18
vidalia_11
Pedigree
What is your experience with VoIP?
With the use case you have in mind?
19
mister b 1138
Availability
Can you hire the right team?
2,921 webrtc
33K rtp
239K sip
841K voip
LinkedIn search for keywords…
20
The innovator’s dilemma
21
Time
Product
Performance
Low end
High end
The innovator’s dilemma
22
Time
Product
Performance
Low end
High end
You are here
Is “basic” media communications your core competency or should you differentiate elsewhere?
Monetization
1. Selling tools
2. Enterprise and UC
3. Consumer messaging
4. Adding context
23
Joshua Davis
Poll Question: In what cases would you choose to use an API platform?
1. Always, no sense in building this
2. When video communication is not the core feature of my service
3. I would use it as long as I can white label it
4. Will not use it, no sense in vendor lock-in
24
Development alternatives Get acquainted with the strategies
25
3
Development Alternatives
26
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
SDKs
• TURN: rfc5766-turn-server
• SIP: • Asterisk, FreeSWITCH, Kamilio • SIPjs, jsSIP, QoffeeSIP, sipML
• Media servers: • Dialogic PowerMedia XMS • GENBAND SPiDR • Jisti Video Bridge • Janus • …
28
Services
29
Signaling
NAT Traversal
MCU
API Platforms
30
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
Poll Question: 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
32
Ben W
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/
Thank You!
34
Tsahi Levent-Levi
http://bloggeek.me
Amir Zmora
http://www.linkedin.com/in/zmora
