When people think about banks, the thoughts that spring to mind are images of serious people in conservative suits, large buildings with marble-floored lobbies and rows of teller windows, and well-fed men who look like the guy on a Monopoly box. Indeed, leading banks have always worked hard to maintain stellar reputations for reliability, safety, and longevity. You don’t tend to think about banks being big risk-takers, or experts at trying out new business practices or cutting edge technologies.
But when you look a little closer, the truth is, leading banks are expert at understanding and taking calculated risks, which is essential to their core business of taking deposits from some customers and prudently loaning out those funds to others. They are also remarkably forward-looking in trying out new technologies and business innovations, even if they don’t always portray themselves this way.
When creating new services and products, organizations always face a challenge whether to buy or build key underlying components and functionality. As WebRTC attracts an increasing degree of interest, we regularly hear from customers that they are considering the trade-off around the decision to buy or build. Many go so far as to try and build their own real time video or audio solution before they turn to a hosted platform like OpenTok. Not surprisingly given the business we are in, we come down pretty strongly on the side of leveraging a hosted service.
WebRTC is changing the way enterprises communicate within their organization and with their customers.
As a result of the large and diverse range of different use cases of WebRTC in the Enterprise world, there are inevitably a number of challenges that need to be addressed. We’ve compiled a list of some of the key challenges and solutions for consideration with regards to implementing WebRTC for Enterprise solutions: Signaling, Multi-party, Interoperability, Quality and Scalability.
SIP? XMPP? JSON? Rumor? The right answer to the signaling question probably depends a lot on your starting point and on what you’re trying to accomplish.
While many people think signaling should be standardized; others think we already have the answer in SIP or REST. Some maintain that the lack of a signaling specification (beyond the need to support SDP offer/answer) is a huge gap in the WebRTC standard.