Webinar: To Build or Not To Build Your WebRTC Infrastructure
•
0 likes•355 views
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.
Recommended
Recommended
More Related Content
What's hot
What's hot (9)
Similar to Webinar: To Build or Not To Build Your WebRTC Infrastructure
Similar to Webinar: To Build or Not To Build Your WebRTC Infrastructure (20)
Recently uploaded
Recently uploaded (20)
Webinar: To Build or Not To Build Your WebRTC Infrastructure
- 1. To Build or Not to Build Your WebRTC Infrastructure June 2014 Tsahi Levent-Levi
- 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
- 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:
- 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
- 25. Development alternatives Get acquainted with the strategies 25 3
- 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
- 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
- 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
- 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
Editor's Notes
- 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