You can't compare communications platform as a service to Web Real-Time Communications. WebRTC is a piece of technology,...
not a service. It is a building block that works with other components to comprise the technology stack used in an application or service. WebRTC support deals with embedded communications, so you might think of it as competing with, or complementary to, communications platform as a service, or CPaaS.
If you are trying to build a product that needs communications functionality, you can use a CPaaS vendor to manage embedded communications for you, letting you focus on your product and user experience instead. It is within the same concept of using Amazon Web Services instead of purchasing physical machines and putting them in a data center.
Most CPaaS vendors support WebRTC in one way or another, because WebRTC enables them to add web browsers to the list of devices they support for embedded communications. The question then becomes: Which CPaaS vendor should you choose that will also cover the requirements you have for WebRTC?
Alternatively, you could use a separate vendor for WebRTC, or develop that part on your own instead of buying that capability from a single vendor.
Do you have a question for Tsahi Levent-Levi or any other experts? Ask your enterprise-specific questions today! (All questions are treated anonymously.)
How to choose the right CPaaS offering
How CPaaS streamlines embedded communications
SDKs, servers, platforms boost WebRTC library