DOCUMENTATION
Why Real Time Web?
Limitations of today’s Web architecture and why a shared model for live resources is needed.
The Internet and the World Wide Web were not originally designed for a world containing billions of continuously changing sensors, actuators, autonomous machines, AI agents, and user-controlled data sources.
Limitations of today’s Web
The World Wide Web is highly effective for publishing and retrieving information, but several limitations become apparent when it is applied to live machines and resources:
- Hyperlinks are primarily one-way relationships.
- Live bidirectional communication requires additional technologies.
- Sessions, identity, authentication, and trust are repeatedly implemented by individual services.
- Resource ownership and access control are often delegated to centralized platforms.
- Data is frequently copied from its source and stored by intermediaries.
- APIs are commonly designed for a particular provider, application, or data model.
- Integrating heterogeneous systems requires extensive middleware and custom development.
APIs have made machine-to-machine communication possible across many different systems. However, an API normally exposes a predefined interface controlled by a particular service provider. Consumers must adapt to that interface, authenticate with that provider, and rely on the provider’s infrastructure and data model.
As the number of connected resources grows, this approach can produce a fragmented landscape of APIs, databases, authentication systems, cloud platforms, and proprietary integrations.
What fragmentation looks like
Today, these resources are commonly connected through cloud platforms, APIs, middleware, and centralized databases. The result is an environment in which:
- Live data is repeatedly copied and stored in different systems.
- Applications depend on provider-specific APIs.
- The same integrations must be developed many times.
- Users often surrender control over their data to centralized platforms.
- Devices and services cannot easily understand or communicate with one another.
- Identity, authentication, payments, and trust are implemented separately for each service.
- AI agents and autonomous machines lack a common environment for discovering and interacting with live resources.
A shared architecture
RTW addresses these challenges by providing a shared architecture for directly addressable, bidirectionally connected resources. Its purpose is to make live resources easier to discover, authorize, combine, transform, and use across organizational and technological boundaries.
A is not controlled by a single entity. It evolves continuously as independent participants connect and manage their own domains and services. Each participant contributes to a collective, self-growing ecosystem while retaining control over its own resources.
This gives creators and developers the freedom to build new services without requiring the entire network to adopt one vendor, one data model, or one centralized platform.
Does RTW replace the Internet?
No. RTW is designed to operate on top of and alongside the existing Internet.
The Internet provides the underlying global infrastructure for transporting data. The World Wide Web provides an established system for publishing, linking, and retrieving information. RTW uses this existing foundation while adding mechanisms for live, bidirectional relationships between physical and virtual resources.
A conventional website can continue to deliver documents, images, and videos, while RTW can provide live data channels and interactions behind or alongside that website.
The longer why sits next to this page: The Internet of tomorrow. Next in this path is Data and information. The lamp story is in the journal Two webs.