NKP - NetKernel Protocol
NetKernel Enterprise Edition features the NKP (NetKernel Protocol) infrastructure.
NetKernel Prototcol (NKP) is designed to transparently relay requests between NetKernel instances.
NKP supports long-lived transparent bridging of NetKernel address spaces. In addition NKP supports instantaneous
"oneshot" stateless requests betwen client and server.
What makes NKP unique as a protocol for cloud server configurations is that it seamlessly distributes the NetKernel ROC abstraction
across a physical set of servers. Features include:
- Transparent ROC request injection into the remote address space.
- Full contextual spacial scope that spans client and server. Just as with the local ROC spacial scope, a server-side endpoint can make resource requests back in to the client "superstack" address space. (Client-Server inversion)
- Contextual transient cloud convergence - if A is talking to B and A talking to C then, B can talk to C (with appropriate trust constraints).
- Full support for distributed representation caching with distributed dependency model.
- Full client-side support of NetKernel endpoint metadata from the remote side. (No need for WSDL or UDDI style - what you see is what you execute).
- Dynamic client-side discovery and integration of remote-side documentation and unit tests.
- Support for transfer of indefinitely large representations.
- Transparent and configurable compression.
- Support for publish and subscribe style architectures.
- Support for request header propagation and sticky headers.
- TLS/SSL secure sockets
- Pluggable authentication of connections.
- Asynchronous (threadless) client and server - scaling to very large numbers of connections with very light weight client/server resource requirements.
- Architectural load balancing and throughput shaping components (eg asynchronous throughput throttle etc).
- Very simple to set up and manage
- Very high performance.
A comprehensive set of documentation for NKP is available here.