Tuesday 19 April 2011

Who cares...

I believe that the applicability for HTML5 WebSockets is very broad. Whilst today we're seeing considerable uptake in the next generation of RIAs being built, I can see a day very soon when WebSockets will be leveraged in a myriad of ways that we couldn't imagine with yesterday's Web.

So here is a random list of large software and infrastructure companies, beyond just the browser vendors, that I believe do (or should) care about HTML5 WebSockets in a big way, and why.

Google: The Google view of your world is everything on their servers, and your online life lived through the Chrome browser, Chromium (on a laptop), or Android (on a phone/tablet). Everything Google provides is essentially Web or Cloud based. Search, GMail, Google Docs, Maps, Latitude, Wave (before it was canned), Picasa, etc. If your Google life is to be lived within the browser, then surely WebSockets constitutes the best communication fabric to connect you with your data and your rich, dynamic, online collection of life tools. The reduction in network bandwidth and latency resulting from moving from HTTP polling to WebSockets means huge savings for the likes of Google hosting these sorts of apps. The ability to do data and application aggregation directly in the browser (or mobile device) rather than at a Portal server simplifies the architecture.

Apple: With the proliferation of iOS devices, and a dislike of Adobe Flash, Apple are making big noises in the HTML5 movement, with good reason. Connecting your iOS device with iTunes, MobileMe and onboard apps with associated data requires low latency, efficient, bi-directional connectivity. Whether you're tethered, WiFi or cellular, WebSockets is ideal for providing Web connectivity for these devices. Apple built a massive new data centre for a reason; to host a lot of your online world there.

Cisco: For two reasons. Because they own technologies like WebEx that would benefit from using HTML5 technologies to provide a rich in-browser experience without the need for plugins. And also because I believe WebSockets are "TCP for the Web". So if you're the biggest player in TCP infrastructure in town, you'd care about owning that space in and across the Cloud.

Messaging Vendors: Business (or Enterprise) Messaging for the Web is the next big thing for these guys. Being able to extend the reach of critical business messaging technologies out across the Web and across the Cloud will drive a new wave of business applications that provide a broad reach of business-to-business connectivity. Some or all of these vendors have already highlighted the fact that messaging for the Web is their new hot topic. The likes of Tibco, Informatica (29West), IBM and Solace could benefit from using WebSockets to extend the reach of their existing messaging systems to the Web and across the Cloud in a real-time, efficient manner. No more de-coupling at the web middleware layer and relying on HTTP. Reduced latency, reduced bandwidth, increased proliferation of vital business data.

Citrix: Extending the reach of business applications is big business. Doing it securely and across the Web is hard. It requires special software, plugins, client-side bits and pieces and lots of security configuration. Secure WebSockets extends the reach of any business application and it's associated communication protocol across the Web seamlessly, no plugins required. Drive those apps in-browser or on Desktop and let WebSockets be the technology that "placeshifts" the app and it's data to where you are, securely. Bye bye VPN, bye bye heavy thick client installs.

Microsoft: From a heritage of pushing back against adoption for open standards (I know, I used to work at Netscape during the first browser war), to a modern Microsoft who have one of the better HTML5 enabled browsers in IE9 and (preview) IE10. The dinosaur uses it's weight to drive forward an important new standard. If future generations of Office are going to be cloud-based, subscription models, driven through IE, then WebSockets will be the best piece of tarmac between you and your next Word doc or Powerpoint preso.

Social Networking: Don't even get me started on the amount of infrastructure Facebook, Twitter, Zynga, etc could all save if they moved to WebSockets. The dramatically improved, richer user experience they could deliver by sending all their data over WebSockets is just a bonus.

The list goes on. Those are just a few examples. However one constant fact remains; HTML5 WebSockets are going to be doing things on the Web that will revolutionise how we communicate tomorrow.

I believe the future for WebSockets is very bright, and it's happening now.

No comments:

Post a Comment