Dream

Poster Content
nk4um Administrator
Posts: 607
November 7, 2006 16:00Comparisons
Guizmo I''ll prefix my comments with the fact that I haven''t looked at the Dream product but only glanced at their website. It is interesting to observe the comparison from their perspective.

It seems we agree that simple is good and REST has merit.

The first major difference I see is that their intent is fundamentally different:

Dream is a REST-based distributed application framework...

NetKernel is a resource-oriented microkernel...

i.e. NetKernel makes no attempts to be a distributed platform at it''s core. Netkernel provides many capabilities to integrate to networking technologies and protocols but it is not itself a means to distribution.

The second major difference is that Dream appears to be focuses at delivering REST web services and web applications. NetKernel is a general purpose platform that leverages benefit from the REST principles which underly its operation. It''s abstraction provides a general purpose computing platform that provides web-like scalability and micro-cacheability. It acheives this through the embodiment of a services communicating in an asynchronous messaging-passing environment.

I don''t think it makes much sense to dig down into micro level comparison of features when each products premise is different.

Licensing
I''d like to take a moment to clarify our licensing position. NetKernel is dual licensed. Our public license is indeed reciprocal and does re-enforce the idea that using NetKernel in a royalty free, open-source way requires that derivative use is also open sourced with an OSI open license of your choice. We belive that this strengthen the open source community. However we understand the need to offer possibility for NetKernel to be used in commercially sensitive applications where exposing the source is not in the best iterests of  its developer. Hence we also offer flexible commercial licensing terms too. Commercial licensing aids ongoing research and development into NetKernel and ensures it will continue to be a compelling product well into the future.

NetKernel is written in JavaTM not Beanshell. However the NetKernel infrastructure is independent of the languages supported over it''s infrastructure. Netkernel supports a wide range of procedural and declarative langages which can be used to code services or orchestrate services.





Like · Post Reply
nk4um User
Posts: 31
November 7, 2006 14:34Dream
Here is a post about drawing the first differences between Dream and NetKernel
http://www.opengarden.org/dream/technical_discussions/differences_between_dream_and_netkernel

Just for those who do not know Dream : MindTouch Dream is a REST-based distributed application framework developed in Mono/.NET. With Dream, a Web service is similar to an object, and features interact through standard HTTP verbs. Dream manages all the complex aspects of interactive web services, such as providing storage locations, database connections, event notifications, automatic data conversion from XML to JSON and short-circuit communication for co-hosted services.

I don''t know yet but i feel some kind of disagreements :
1. I agree on their licence talk but regarging "it''s possible to make highly reusable code without losing type information. This makes maintenance much easier." i don''t know NK in depth yet but my NK reading investigation seems to reveal component oriented development in NK so reusable code. Am i wrong ?

2. Then for "Finally, and more importantly, Dream is about REST and making things simple. A dream service requires less than 10 lines of code, because it focuses on making the most common case as streamlined as possible." NK website insists on the a) NK is Restful, b) the NK simplicity and fewer code is generally needed against some others architectures or technologies. Am i wrong again ?

3. "NetKernel is written in Beanshell". Here i don''t know but i don''t see what it could implies negatively.

Like · Post Reply