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.

1. To Build or Not to Build Your
WebRTC Infrastructure
June 2014
Tsahi
Levent-Levi

2. Tsahi Levent-Levi
http://bloggeek.me
tsahil@bloggeek.me
2
Amir Zmora
http://www.linkedin.com/in/zmora
amzmora@gmail.com

3. Many factors to consider
3
Business Technical

4. Business Criteria
• Nature of your business
• Feature/Core
• Business model
4
Wikimedia

5. Technical Criteria
• Island
• Open/closed service
• Geographical distribution
• SLA requirements
5
pixabay

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

9. How are Calls Made with WebRTC?
9
1
2
3
4
5

10. What does it provide?
• Real-time
• Voice, video and data
• Browser based
• No plugins
• Secured
• Interoperable (between browsers)
10

11. Why all the fuss?
11

12. 12
So What’s
Missing?

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:

15. Boundaries of WebRTC
15
Infrastructure
Signaling
Media Processing
Codecs
Source:

16. An inherent tension
16
VoIP
RTC
WWW
Web
jasoneppink

17. Build vs Buy
Why would you choose one over the other?
17
2

18. Requirements
• Voice or Video?
• Messaging?
• Multipoint?
• Mobile Devices?
• Recording?
• Storage?
18
vidalia_11

19. Pedigree
What is your experience with VoIP?
With the use case you have in mind?
19
mister b 1138

20. Availability
Can you hire the right team?
2,921 webrtc
33K rtp
239K sip
841K voip
LinkedIn search for keywords…
20

21. The innovator’s dilemma
21
Time
Product
Performance
Low end
High end

22. 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?

23. Monetization
1. Selling tools
2. Enterprise and UC
3. Consumer messaging
4. Adding context
23
Joshua Davis

24. Poll Question: In what cases would you
choose to use anAPI 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

25. Development alternatives
Get acquainted with the strategies
25
3

26. DevelopmentAlternatives
26

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

28. 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

29. Services
29
Signaling
NAT Traversal
MCU

30. API Platforms
30

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

32. 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

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/

34. Thank You!
34
Tsahi Levent-Levi
http://bloggeek.me
tsahil@bloggeek.me
Amir Zmora
http://www.linkedin.com/in/zmora
amzmora@gmail.com