CafeX made an announcement this week-end about their new Japanese partnership, allowing them to extend their sales reach to North and South-East Asia. Just as I had put the final touch on my “webRTC in Asia report“, with a special section on Japan with analysis of Dialogic and Twilio approach to doing WebRTC Business in Japan, another event that just stresses the importance of Asia for WebRTC vendors.
Recurrently, people are arguing on different webrtc mailing lists or social sites. Some questions are still left open: which MCU/SFU is better, which PaaS is better, should one work on webRTC in Safari? in Edge? Usually some kind of statistics is being used. While it is well known that you can make statistics say whatever you want them to, I do not always see reason to argue. Indeed, most of the time people argue about different use cases that are not opposed to each other, or implicitly define different scopes that do not overlap. I thought it would be good to clarify things a little bit by presenting several trustable source of data for browser usage, webrtc support, and define a view usual use cases for illustration.
Apple was represented by a dozen of employees at the W3C TPAC in September. The fact that it was held in sunny Lisbon late September might explain the surge in interest, in any case we were very happy to have them with us. I usually try to meet with the WebRTC team once a quarter, and we took this opportunity to go over the latest Q4 news that can be made public. Toward the end of the post, I will also give away some of my tricks to monitor public WebRTC activity in webkit.
This is a translated, adapted version of an original post by NTT’s Iwase Yoshimasa available here, with agreement from the author. As the ecosystem move quickly, some updates were added in blue and in italic.
This post describes the current state (as of september 2016) of MCU and SFU media servers used in WebRTC solutions. I hope it will serve as a quick reference for those wanting to know more about the concepts and the available projects. The details of each product introduced here are not provided, but a link to each product is, so you can read further if you want. Moreover, we almost only mention stand alone media servers, and did not touch on webRTC CPaas or PaaS.
My attending W3C TPAC in Lisbon, portugal, this week signs the end of my european webrtc teams tour. This post will be the first one reflecting the meetings I had. Janus has always been an interesting project. Technically, the fact that it is written in C and very small makes it one of the best server for IoT (kurento or jitsi would be less suited). Its plug-in/extention architecture, not only keep it even leaner, but also allows to very easily build different types of media server (MCU, SFU, …) or app server (SIP Gateway, …). The IETF leveraging them to replace webex for their meetings (thousands of attendees each) and slack for their infrastructure, not only validated their product but also the market, and business viability. The danger of course is to be ONLY influenced by what I read, or people I consult for, which admittedly is too small a subset to draw any reasonable conclusion from. So I decided to hear from them.
Every month I received a certain number of newsletters from different companies. Some are really …, hum, …. entertaining with their claims. Today’s batch reminded me that one year ago almost, I published on linked in (only) some numbers for those who wanted to evaluate webRTC PaaS. It looks like it is still needed today. So here you go. [Updates and comments of the original text will be placed in italic and between braces.]
One of the most difficult thing nowadays is to read through some (web)RTC announcements. Just like everyone is claiming to be a visionary leader in LinkedIn, every companies in the space (and their moms) are “leader in the market”, “Best in their space”, “Last independent webRTC platform”, “with better technology and scalability than Twilio/Tokbox/AWS/God”. Right.
Intel has come a long way since 2013/2014 with their collaboration Suite for WebRTC. Today they propose one of the most complete free solution, practically a PaaS-in-a-box:
- web (+IE plugin), mobile and windows clients,
- a complete infrastructure
- Media server
- both MCU and SFU modes,
- multi-party and broadcast
- SIP Gateway.
- Media server
This post will provide some insight on what they propose, the evolution of their offer, and what’s coming next.
For once, a blog post about something else than webRTC.
Back in 2013, I did a full review, including benchmarks, of all the open source webRTC media servers. Defining use cases and corresponding tests and benchmarks was hard, and while I was happy with the results, which I presented a couple of times in conferences, the results are now grossly outdated. A year and a half ago, I tried to trigger a gathering of all the actors, as they all belong to IETF. It is very difficult for a potential user to know which project to use, and answers on the webrtc-discuss mailing list were confusing at best. We needed something more descriptive, easier to understand. I got traction from most of the players, but couldn’t make it happen. This year, hopefully, things will be different.