Loose Coupling

Loose coupling is an overused term in the industry. In NetKernel it has real substance.

In NetKernel, URI addresses are resolved for each request. This model ensures that all resources, including code, are dynamically linked at the moment each request is processed. The URI addressing model creates a layer of indirection that is uniformly and pervasively available to NetKernel systems. This contrasts with more static environments where links between program elements are made once and then not changed (such as with C, C++, Java, and most other environments).

The management of the URI address mapping can be delegated to code (see, for example, the mapper pattern) which means that even the relationship between resources can be dynamically computed as part of an application.

The URI addressing model allows for temporal loose coupling - that is, 'future proofing'. It is straightforward for a resource to return a static representation and then change that to a dynamically generated resource by changing the code behind the URI address. This can even be done in a live production system without dropping any requests.

The addressing model also permits any number of addresses to refer to the same resource. This multi-valency of the address space means that naming can be preserved for legacy systems while newly developed systems can use a new set of names. This capability is critical for smooth management of system expansion, growth and evolution.

Perhaps the most intriguing property is reconfigurability with respect to location. Resources can be relocated or multiply located in the logical URI address space without regard to physical constraints.