|By Kaazing Blog||
|January 29, 2013 01:29 PM EST||
After presenting to a partner of Kaazing last week I got asked what impact the emerging WebSocket standard would have on the Web, assuming we continue down the path that has already been laid out.
The impact could be the same, or even more profound, as when we were first introduced to HTTP as a means to share static documents. The difference is that this time the targeted market is already defined – it is called the Web. I have over the past several years, half jokingly and half seriously, compared the current static Web with a push to talk radio (aka Walkie Talkie) and the new living Web with a cell phone. You can get by with the WT and solve most of your problems; after all it’s been around for a while and it works. If you want to communicate with a friend in “real-time” you can solve it by getting two WTs, one to talk and one to listen. With a new Web standard, WebSocket, entering the market, Web developers now have access to the equivalent of a cellphone – one channel for “talk” and “listen”.
What would you choose if both push-to-talk and cell phone were available to you? What would developers choose if both technologies were readily available to them (e.g.: browser support)?
Well, if you are uncertain and feel like WebSocket is an unproven standard you might want to relate to this; remember the first time your friends started pushing you to buy a cellphone although you already had a stationary phone at home and one at the office that worked perfectly? Now several years later we all have at least one cell phone, each, and we can’t (at least I can’t) live without it.
This is exactly the same impact the following line of code will have on the Web in comparison with the current HTTP communication we are so used and accustomed too.
var mySocket = new WebSocket("ws://websocket.org/");
If you do understand the profound impact this one line of code will have you are in good shape and most likely are already using, extending, or pushing this new standard solution from W3C and IETF. If you are not, then let me take a short moment to explain why it is so important:
- HTTP was designed to deliver static documents, not to deliver transactional, dynamic, and real-time data updates.
- HTTP is by design stateless, so session state needs to be artificially maintained. Traditionally this is done by a legacy Web-tier solution such as an application server like Oracle WebLogic Server or IBM WebSpere.
- In every environment developers have access to a “socket” interface, which enables them to communicate using any format (read protocol) over a full-duplex connection. Not on the Web.
- Not having access to a standard, Web-friendly, socket API forces us to create transformation layers when sending data from a Web client, using HTTP, to a backend system relying on a different full-duplex TCP protocol e.g. XMPP, STOMP, AMQP.
- The above line of code opens the floodgates to use any TCP-based communication format, which in turn enables developers to freely innovate and create new types of Web applications that previously have not been feasible over the existing HTTP infrastructure.
- WebSocket offers a far better use of bandwidth by getting rid of unnecessary HTTP headers when information is shared. The improvement is at a ratio of up to 1000x.
- The latency to deliver data is greatly improved by eliminating the round trip of the HTTP request-response model, and by using the bandwidth more efficiently.
With the explosive growth of Web-enabled devices (yes, I’m thinking about the iPhone, iPad, Android, Galaxy, etc…) and the demand for more and live information, communication and distribution of data over the Web is growing exponentially. At this rate the growth of data distributed over the Web will out pace the performance principals of Moore’s Law, which we depend on to ensure that our hardware can keep up with our needs.
WebSocket traffic vs. HTTP traffic
For individuals this may not be too much of a concern, but for companies providing online services it will be, and already is, a huge and costly issue since it requires a tremendous amount of resources to deliver on the increasing demand for live information over the Web (read about Google’s move and Facebook’s move).
For example, when a user enters a single character ‘a’ in a search engine, a drop down list appears automatically showing possible search results starting with letter ‘a’. Behind the scenes an HTTP request has been issued asking the server for the information displayed in the drop down list. For every new character entered a new HTTP request is issued to the server to request for more information. The same HTTP characteristics you can find in collaborative online documents such as Google Docs, where each character entered generates a POST to ensure that users editing or looking at the same document can see each other changes in real-time.
Now, what was sent, what was received, and what was really needed?
There is a great article on websocket.org, called a “Quantum Leap in Scalability for the Web” that is outlining the difference between HTTP and WebSocket in terms of bandwidth utilization. In this article the sample application is a simple trading solution, but the math can be applied to any HTTP-based dynamic and transactional Web application.
In the article we have 0,665Gbps in header traffic to respond to 100,000 users per request.
What is the impact of using WebSocket technology? There are no sizable headers involved passing information between a client and a Websocket Gateway. Let’s apply the above math example to WebSocket technology as described by the article:
100,000 visitors receiving an update every second. (WS wireframe = 2 byte) * 100,000 * 8 = 1,600,000 bps (0.001526Gbps).
Results from this easy math:
HTTP:// = 0,665Gbps versus WS:// = 0.001526Gbps. In the above sample Websocket communication is 436 times more efficient. 436 times! We are talking about a gigantic leap of improvement, and that assuming that your cookies are not adding more data than this sample.
WebSocket is not a better Ajax!
Not only is the new standard improving bandwidth utilization it also gives us the ability to use any TCP-based high level communication format for our Web applications. This part of the HTML5 WebSocket standard has still yet to be fully appreciated. Right now most solutions and developers tinkering with the WebSocket APIs are looking at the new standard as merely a better replacement of XHR, or Ajax, when in fact it is a quantum leap forward in communicating over the Web that cannot be compared to XHR. With WebSocket we can now build client libraries in any Web technology supporting any TCP-based protocols. A simple example would be to extend the now widely used chat protocol XMPP to the Web (here is a demo site that lets you log in to Google Talk using XMPP over WebSocket) by providing a client-side implementation on top of Websocket APIs, or an advanced example would be to extend Java Message Service (JMS) over WebSocket such as the Kaazing WebSocket Gateway.
Scaling a WebSocket Solution
Web developers have been trying to work around the limitations of HTTP since the early days using techniques such as Comet, Reverse Ajax, or HTTP Streaming. With a move to persistent connections, or a stateful Web, server scalability of concurrent connections has been, and still is, a serious concern. Holding on to a thread on the server while the thread is not in use, combined with an Web-tier and infrastructure that was not designed for this, is not necessarily a scalable combination. Now, great strides have been made to ensure better scalability across technology stacks such as the use of NIO in Java.
At Kaazing we have always taken scalability and performance extremely serious and focused on making sure that our software is not in the way of scale or performance. As a matter of fact, we did a benchmark over the new year 2008/2009, to prove that scaling a WebSocket solution with persistent connections was not an issue, so we brought in a Java performance expert – Kirk Pepperdine – to help us and by the first weeks of Jan 09 we were running 1,000,000 concurrent connections on one single server. Now, is this practical? A more realistic scenario is running 1,000,000 users on a single rack or half a rack. This would enable us to have failover and high-availability, while still providing great performance and scale. So, last year we ran new tests together with DELL and Tibco to ensure not only great scale but also outstanding performance: DELL, Tibco, and Kaazing enable ‘The Fastest Million’ to revolutionize real-time data delivery over the Web.
The simplest design ideas are often the innovations with the most impact. WebSocket as an idea and design is extremely “simple” and its impact on our industry will be profound. Of course, with simple ideas you also get the “doubters”. I remember one time when my co-founder John Fallows and I met with a renowned VC in Silicon Valley and he asked us:
“If this is such a great idea why has no one come up with this idea before?”
I guess you could ask humanity a similar question about why it took several thousands of years to invent the wheel – after all it’s so obvious and simple.
What is important to understand is that we now have at our disposal a very powerful tool that will enable us to communicate securely with anything over the Web, and that it is only our own imagination that will limit our ability to fully exploit the WebSocket standard to its full potential.
If you are having performance and scalability issues with your current Web solution then it is time to look at an enterprise WebSocket platform, such as the one Kaazing provides. To round off I’m just going to ask you one short question:
If you had a choice between building a Web application using HTTP and Websocket, and both were readily available to you, which one would you choose?
Who are you? How do you introduce yourself? Do you use a name, or do you greet a friend by the last four digits of his social security number? Assuming you don’t, why are we content to associate our identity with 10 random digits assigned by our phone company? Identity is an issue that affects everyone, but as individuals we don’t spend a lot of time thinking about it. In his session at @ThingsExpo, Ben Klang, Founder & President of Mojo Lingo, discussed the impact of technology on identity. Sho...
Jan. 18, 2017 03:45 AM EST Reads: 3,993
Technology vendors and analysts are eager to paint a rosy picture of how wonderful IoT is and why your deployment will be great with the use of their products and services. While it is easy to showcase successful IoT solutions, identifying IoT systems that missed the mark or failed can often provide more in the way of key lessons learned. In his session at @ThingsExpo, Peter Vanderminden, Principal Industry Analyst for IoT & Digital Supply Chain to Flatiron Strategies, will focus on how IoT depl...
Jan. 18, 2017 02:30 AM EST Reads: 1,820
Data is an unusual currency; it is not restricted by the same transactional limitations as money or people. In fact, the more that you leverage your data across multiple business use cases, the more valuable it becomes to the organization. And the same can be said about the organization’s analytics. In his session at 19th Cloud Expo, Bill Schmarzo, CTO for the Big Data Practice at Dell EMC, introduced a methodology for capturing, enriching and sharing data (and analytics) across the organization...
Jan. 18, 2017 02:15 AM EST Reads: 3,215
With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now ...
Jan. 18, 2017 01:30 AM EST Reads: 4,202
WebRTC is about the data channel as much as about video and audio conferencing. However, basically all commercial WebRTC applications have been built with a focus on audio and video. The handling of “data” has been limited to text chat and file download – all other data sharing seems to end with screensharing. What is holding back a more intensive use of peer-to-peer data? In her session at @ThingsExpo, Dr Silvia Pfeiffer, WebRTC Applications Team Lead at National ICT Australia, looked at differ...
Jan. 18, 2017 01:15 AM EST Reads: 4,891
The cloud market growth today is largely in public clouds. While there is a lot of spend in IT departments in virtualization, these aren’t yet translating into a true “cloud” experience within the enterprise. What is stopping the growth of the “private cloud” market? In his general session at 18th Cloud Expo, Nara Rajagopalan, CEO of Accelerite, explored the challenges in deploying, managing, and getting adoption for a private cloud within an enterprise. What are the key differences between wh...
Jan. 18, 2017 01:00 AM EST Reads: 6,046
"ReadyTalk is an audio and web video conferencing provider. We've really come to embrace WebRTC as the platform for our future of technology," explained Dan Cunningham, CTO of ReadyTalk, in this SYS-CON.tv interview at WebRTC Summit at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Jan. 18, 2017 12:00 AM EST Reads: 2,259
In 2014, Amazon announced a new form of compute called Lambda. We didn't know it at the time, but this represented a fundamental shift in what we expect from cloud computing. Now, all of the major cloud computing vendors want to take part in this disruptive technology. In his session at 20th Cloud Expo, John Jelinek IV, a web developer at Linux Academy, will discuss why major players like AWS, Microsoft Azure, IBM Bluemix, and Google Cloud Platform are all trying to sidestep VMs and containers...
Jan. 17, 2017 11:00 PM EST Reads: 637
IoT is at the core or many Digital Transformation initiatives with the goal of re-inventing a company's business model. We all agree that collecting relevant IoT data will result in massive amounts of data needing to be stored. However, with the rapid development of IoT devices and ongoing business model transformation, we are not able to predict the volume and growth of IoT data. And with the lack of IoT history, traditional methods of IT and infrastructure planning based on the past do not app...
Jan. 17, 2017 10:30 PM EST Reads: 748
The many IoT deployments around the world are busy integrating smart devices and sensors into their enterprise IT infrastructures. Yet all of this technology – and there are an amazing number of choices – is of no use without the software to gather, communicate, and analyze the new data flows. Without software, there is no IT. In this power panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, Dave McCarthy, Director of Products at Bsquare Corporation; Alan Williamson, Principal ...
Jan. 17, 2017 10:30 PM EST Reads: 2,373
WebRTC has had a real tough three or four years, and so have those working with it. Only a few short years ago, the development world were excited about WebRTC and proclaiming how awesome it was. You might have played with the technology a couple of years ago, only to find the extra infrastructure requirements were painful to implement and poorly documented. This probably left a bitter taste in your mouth, especially when things went wrong.
Jan. 17, 2017 09:15 PM EST Reads: 7,566
SYS-CON Media announced today that @WebRTCSummit Blog, the largest WebRTC resource in the world, has been launched. @WebRTCSummit Blog offers top articles, news stories, and blog posts from the world's well-known experts and guarantees better exposure for its authors than any other publication. @WebRTCSummit Blog can be bookmarked ▸ Here @WebRTCSummit conference site can be bookmarked ▸ Here
Jan. 17, 2017 08:00 PM EST Reads: 11,649
A critical component of any IoT project is what to do with all the data being generated. This data needs to be captured, processed, structured, and stored in a way to facilitate different kinds of queries. Traditional data warehouse and analytical systems are mature technologies that can be used to handle certain kinds of queries, but they are not always well suited to many problems, particularly when there is a need for real-time insights.
Jan. 17, 2017 06:45 PM EST Reads: 6,232
Providing secure, mobile access to sensitive data sets is a critical element in realizing the full potential of cloud computing. However, large data caches remain inaccessible to edge devices for reasons of security, size, format or limited viewing capabilities. Medical imaging, computer aided design and seismic interpretation are just a few examples of industries facing this challenge. Rather than fighting for incremental gains by pulling these datasets to edge devices, we need to embrace the i...
Jan. 17, 2017 05:15 PM EST Reads: 3,573
Web Real-Time Communication APIs have quickly revolutionized what browsers are capable of. In addition to video and audio streams, we can now bi-directionally send arbitrary data over WebRTC's PeerConnection Data Channels. With the advent of Progressive Web Apps and new hardware APIs such as WebBluetooh and WebUSB, we can finally enable users to stitch together the Internet of Things directly from their browsers while communicating privately and securely in a decentralized way.
Jan. 17, 2017 04:45 PM EST Reads: 3,057
Fifty billion connected devices and still no winning protocols standards. HTTP, WebSockets, MQTT, and CoAP seem to be leading in the IoT protocol race at the moment but many more protocols are getting introduced on a regular basis. Each protocol has its pros and cons depending on the nature of the communications. Does there really need to be only one protocol to rule them all? Of course not. In his session at @ThingsExpo, Chris Matthieu, co-founder and CTO of Octoblu, walked through how Octob...
Jan. 17, 2017 04:30 PM EST Reads: 2,912
The Internet of Things can drive efficiency for airlines and airports. In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect with GE, and Sudip Majumder, senior director of development at Oracle, discussed the technical details of the connected airline baggage and related social media solutions. These IoT applications will enhance travelers' journey experience and drive efficiency for the airlines and the airports.
Jan. 17, 2017 04:15 PM EST Reads: 1,992
SYS-CON Events announced today that Catchpoint, a leading digital experience intelligence company, has been named “Silver Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Catchpoint Systems is a leading Digital Performance Analytics company that provides unparalleled insight into your customer-critical services to help you consistently deliver an amazing customer experience. Designed for digital business, C...
Jan. 17, 2017 02:30 PM EST Reads: 1,749
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place June 6-8, 2017, at the Javits Center in New York City, New York, is co-located with 20th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry p...
Jan. 17, 2017 02:15 PM EST Reads: 3,644
In his General Session at 17th Cloud Expo, Bruce Swann, Senior Product Marketing Manager for Adobe Campaign, explored the key ingredients of cross-channel marketing in a digital world. Learn how the Adobe Marketing Cloud can help marketers embrace opportunities for personalized, relevant and real-time customer engagement across offline (direct mail, point of sale, call center) and digital (email, website, SMS, mobile apps, social networks, connected objects).
Jan. 17, 2017 02:00 PM EST Reads: 5,384