Real-Time Web or Right-Time Web?

Real-time and the real-time web continue to be a hot topic of conversation but is the term "real-time" getting used correctly? When we talk about real-time technology are we truly describing what the technology is delivering or is it being used and abused as just another marketing buzz word? Can we class any of the current technology solutions as truly real-time and can other solutions be defined in any other way? Is it too late to save "real-time" or will it forever be lost to marketing?

Back in July 2009 even Wikipedia didn't have a definition for "Real-Time Web" although it was being used by a lot of companies to describe their products and services. Wikipedia does have a definition now and the fundamental top-level definition is:

The real-time web is a set of technologies and practices that enable users to receive information as soon as it is published by its authors, rather than requiring that they or their software check a source periodically for updates.

The key point here is that the information should be received by the users as soon as it is published without the need to periodically check the source for updates. To make this even simpler let's define this as "Push, not Pull".

We've previously discussed real-time technologies and services in our HTTP Streaming v PubSubHubbub article but haven't defined this fundamental point of Push, not Pull. Push should be core to any real-time technology as demonstrated by HTTP Streaming, WebSockets, PubSubHubbub, Webhooks and Comet and as used by real-time client push services and services such as Superfeedr and DataSift. Any event or notification based system needs to use Push in order to instantly deliver information to all interested parties (a User viewing a UI or a 3rd party system). The current version of Real-Time Web on Wikipedia lists a "True real-time web" alternative description which attempts to better define the experience and technologies required to deliver a true real-time web experience but it is in need of some refinement.

What this means is that products, services and systems that currently use a Pull mechanism to deliver data, specifically in the form of polling, within their real-time service or application aren't truly real-time. This doesn't mean that the service or application isn't valuable, it just means they are using technology that does not fall under the definition of a real-time web technology. A few examples of services and applications that use claim to be real-time web solutions but don't use real-time web technology in their delivery of information to the web browser include (and you may be surprised by a couple):

So, what should they call their service is they can't use "real-time"? If instant notification of new data isn't necessary, and a service or application has chosen to use a pull (polling) solution which delivers the data in a timely manner so that it is still useful then I would classify this as a "right-time web" solution. Right-time Web technology should not be confused with the right-time web idea which is about ensuring you get relevant information. Right-time web technology ensure you get the information you are interested in whilst it is still relevant and in a lot of cases polling solutions can achieve this.

Real-time web technologies should be used when the instant delivery of data is required - when seconds or even milliseconds really matter. That's why these technologies have been pioneered in the financial sector and have been in that sector for over 10 years and have only recently moved into wider adoption. There is also an argument that push technology can actually be more efficient than polling since updates are pushed only when new data is available where as polling solutions always make a request at a given interval even if no new data is available leading to wasted client/server round trips.

Right-time web technologies can be used when the instant delivery of data isn't important and when delivering data within a set interval, normally 10, 20 or 30 seconds doesn't impact the value of that data.

It's probably too late for the terms "real-time" and the "real-time web" and as they have already been hijacked and will continue to be used even when the underlying technology, and the experience that is being delivered, isn't truly real-time and would be better being referred to as right-time web solutions. Real-time and the real-time web are instead going to continue to be used as umbrella terms for technologies, services and applications that want to present themeselves as cutting edge so it would appear that real-time web and right-time web technologies are going to continue to be incorrectly synonymous.

Photo by Robert S. Donovan

Be sure to read the next Real Time article: Who Curates the Real-Time Web?


Comments (6)

I believe with the growth of APIs and their usage, frequent polling will cause too much of a burden on the network, and become unsustainable.

API Service Providers will have to evaluate push layers for their APIs to manage network load.

Thus forcing applications to become more real-time by adopting push technologies, and only poll when applicable.

[...] a YAWS server that is built on Erlang.  ProgrammableWeb author Phil Leggetter would call this a right-time server instead of a real-time one, because the service does not use push [...]

@Kin thanks for you comment. I completely agree with your point about the frequent polling becoming a burden on the network - wasted polling round-trips from client to server will simply flood networks with useless traffic.

I'm hopeful that real-time push will soon be seen as not only a "cooler" approach, not only a true real-time approach, but also a much more efficient one too.

[...] is published and simultaneously archived, without the user having to check the source for updates (Leggetter 2011). An example of this includes the instance of an iPhone alerting its user that someone has posted a [...]

[...] have covered real-time technologies in the past. For example, real-time or right time has a good overview of the approaches. Webhooks are a popular approach because they’re [...]

[...] time that the information is published, without the user having to check the source for updates (Leggetter 2011). An example of this would be your iPhone alerting you that someone has posted a status on your [...]