Code First - Summary

You have walked through an introductory tour of NetKernel from the code perspective.

The tour started with a Java implementation of an accessor mapped to the logical address ffcpl:/helloworld. Then you saw how to use scripting languages and finally static resources to implement a "Hello World!" program.

In NetKernel information is paramount and languages are secondary. In the resource oriented computing model, resources are identified by logical addresses within an address space. Only at the moment of a request are logical addresses resolved to a physical endpoint implementation that is run to return an immutable physical resource representation.

This section has started from the low-level physical code that will be familiar to developers. It has gradually moved upwards to the logical level to show how software can be logically addressed just like any other resource. The power of NetKernel really takes off when you discover the resource models included with NetKernel each of which provides a large library of logically addressed services for processing information resources.

Just like in Unix, NetKernel's philosophy is to take small powerful tools and to logically compose these together to create powerful composite solutions. In NetKernel, the software tools themselves and the composite solutions can be written either with low-level Java code or more rapidly with a wide range of dynamic scripting languages.

As you continuing learning about NetKernel and resource oriented computing you will see that system development at the logical level of information is extremely productive and intuitive. NetKernel is different and developers using NetKernel find that the difference is significant. Systems ported from Java J2EE require ten to one hundred times less code while running about three times faster. NetKernel based systems are fully asynchronous but do not require you to think about threads and will scale linearly with the addition of CPU cores.

If you are used to developing systems by writing a lot of code you will have to unlearn some of the knowledge and instincts you have acquired and move up to the logical level. Once you do you will not be disappointed. There are rich sets of patterns at the logical level that can be used to directly express the true intent of a system without getting mired in the details of physical level programming.