So .... you think you know SOA? ... but something just doesn't sit right? ... like maybe you're building great services on quicksand?

Look at NetKernel!

XML Webservices ... REST, SOAP, WS Protocols ... where does it all end, let alone begin?

Look at NetKernel!!

How do you scale up and out ... rapidly adapt to changes in business processes ... build simple and infinitely complex composite, service-based applications?

Look at NetKernel!!!

Run, don't walk to 1060 Research.

Jim Cooper, Fortune 500 Services Architect

"I've finished an evaluation of NetKernel for a project and the news is all good. I love what I've seen, kudos to 1060 Research Ltd on developing what could/should be a significant mover and shaker in the internet services world."

Robert Leftwich, System Architect, Sherman System Solutions

Since I have adopted NK at my company, it has started to fill blanks in much of our architecture.

We use it for two main purposes. Content aggregation and systems integration.

With content aggregation, NK pulls data from one or more sources, possibly applies some rules, and feeds the results to the presentation side systems. One example of this is serving Nutch indexed search results of our content. Another is where we query a RDBMS for relevant documents and then pull together the referenced complex xml fragments from a back-end system, over HTTP, and return merged results.

And with systems integration, we have built a JMS transport that delegates incoming messages to NK services that were built in a transport agnostic way, thus allowing those services to be tested over HTTP with no additional complexity in the service. This particular application is a jewel in our infrastructure, and has replaced all components of our vendor provided ESB (except for CBR services) implementation.

To be honest, we may choose to replace the CBR services with NK as well since NK plus mod-e4x has given us massive productivity gains.

Enterprise Architect with a Fortune 500 Customer

In working with the NetKernel over the past year we have seen great opportunity to significantly reduce both the complexity of our project and future maintenance requirements. The proliferation of documentation on the practical and theoretical side has also made it much easier for us to convey the amazing benefits of using the NetKernel architecture to our users and developers alike.

We have embraced this technology as a means of unifying the several transport technologies used in our project and to provide a single container which acts as both client and server in a true peer to peer fashion.

As time goes on, and our understanding of the concepts behind the NetKernel mature, we see ever increasing ways to better our design and take further advantage of the product. The technology neutral framework upon which the NetKernel has been developed is of great advantage and will considerably increase the awareness of RESTful design. It has truly been worth the time spent to investigate this amazing product.

Dave Butler, Pharm2Phork Consortium

We have several projects now in which we use NetKernel. The biggest one is a management interface on top of our digital object repository of scanned images. This repository is based on aDORe software developed by the Los Alamos Research Library. aDORe exposes metadata and data streams using the OAI-PMH and NISO OpenURL protocols.

We use NetKernel to harvest metadata descriptions of images stored in all our repositories. Using Lucene accessors we index the data and create search and browse interfaces for our end users. At regular intervals we instruct NetKernel to update the Lucene indexes. With all the XML tools in NetKernel we have a very powerful development platform in our environment. Next year we plan to provide access to ten thousands of high quality images. We plan to reach several hundred thousand images in a few years.

We also use NetKernel in small projects. For example, we are creating a "happy" server to test if all our webservices are still up and running on our production machines. A small icon on the users desktop will query the server to check the status of the services. NetKernel will send an SMS to our administrators when something goes wrong.

NetKernel is really our powertool. All this functionality, the URI processing and the caching features made our life so much easier.

Patrick Hochstenbach, University of Gent

"I always avoided learning EJB, as I could never see the point. Now [with NetKernel] I know I won't have a reason to learn it in the future, either"

Steve Loughran committer Apache Ant and Axis SOAP Server. Author of Java Development with Ant.

"The thing I really find amazing about NetKernel is the amount of code we end up writing... or rather the lack of... we now spend most of the time structuring what our products need to do and much less on actual coding."

"...a funny feeling I had when going through the NetKernel learning curve is that code would actually grow smaller."

"The NetKernel model, request based operation, fits very well with our type of products where we basically provide networked interfaces. In the past, we had to use a separate and typically quite heavy library for each type of interface, now we do all this in a much more flexible way with the tools NetKernel gives us."

Frank Boddeke, Edge Technologies BV, OEM Licensee Telecom Sector.

"Its the darnest thing I have ever seen, my head hurts and spins. One end of me is thrilled to bits, the closing bracket on the other end is twitching. In between the two, it reads, "its gonna change the way I do things for good"... I haven't been this excited since Java."

Suhail Ahmed. Author of CORBA Programming Unleashed .

I successfully replaced an existing commercial XML framework with NetKernel for a document-processing service used by several U.S. government agencies. The previously-deployed system was unlikely to meet our scalability or flexibility goals as a wider customer base began to take advantage of this central service.

A quick proof-of-concept version of our twenty-step pipeline demonstrated that in addition to having better performance, NetKernel was a joy to use. The marriage of REST and the notion of Unix pipes is an architectural achievement that facilitates a highly-productive environment in which to sculpt XML-processing systems.

We now have a solid platform to continue extending our features and achieved a 3-4x throughput acceleration on the same hardware with almost no other changes. Not only has the product been top-notch, the 1060 Research team has provided excellent support in helping us quickly reach our goals.

Brian Sletten, Bosatsu Consulting, Inc for US Government multi-Agency project.

Giving some more feedback of my experience with NetKernel... I just love it... :) The first thing that I liked about NetKernel, was the similarities with the JMX concept. A service aggregator container, with the advantage of a microkernel, that decouples the actual service invocation, getting rid of that ugly MBeanServer.invoke(yadda,yadda).

But I do (did?) love JMX. I've used it in several integration projects in telecommunication operators several years ago, and I was very happy, when JBoss chose it to be its primary service aggregator architecture. The "problem" with JMX in some of my integration projects were the tight coupling between service invocations and the tight dependency on the Java Object Model, not to mention the fact that service invocation across a single memory address space, gives you a lot of different challenges when you want your service invocation to be distributed, forcing you to use all those object distribution mechanisms that introduce a lot of complexity and error sources...

That's why I think that NetKernel has a lot of potential, because it solves those problems in a very clear way, and there is a lot of cool design concepts, like the public/private URI address spaces and those xml pipelines among others. With only these two concepts you could implement all those "aspect" design features of the JBoss container like the ejb interceptor chain easily

Rui Gil, Inov

"I would like to let you know, that I was able to develop it within a few hours, just by following your bundled documentation and copying and pasting from your source code of similar components. I would like to give you a big compliment for the comprehensive work you did."

"I'm really amazed by your work. I have some unix background and NetKernel is the first network OS abstraction that seems to me enough robust and simple to build good applications upon."