Resoa Nodes

Resoa Nodes - Service Execution Container, Grid Controller and Rest API Resoa node provides all stuff for server side containers, acting within a grid.

See:
          Description

Most important packages
org.resoa.node This is the main package you need for working with the Resoa Nodes.

 

Other Packages
org.resoa.node.core This is the internal package, providing the implementation of the central gateway logic.
org.resoa.topology.service This package contains the Resoa internal service implementations, defined within the resoa.topology.xsd.

 

Resoa Nodes - Service Execution Container, Grid Controller and Rest API

Resoa node provides all stuff for server side containers, acting within a grid.

The central interface for all node implementation is the ResoaGateway. The different node type behavior comes up from different interface implementations. Currently the following implementations are available:

Nodes should be run by using the Resoa 'runner utils', like the org.resoa.util.ResoaRunner or the Console-/DaemonRunners, defined within the root packages. They heavily use the ResoaClassLoader for setting up the internal service container. Look to the example runtime scripts to learn more about the main dependencies, a node needs for startup.

ResoaNodeGateways offer a ResoaPersistence interface to every service implementation, this way a database storage is fully integrated within the framework. The resoa.persistence project offers a JSON based storage solution, running inside the resoa grid. ACID transactions, object relation resolution and grid wide storage synchronization are some very nice features, finally removing the 'SPOF' and bottleneck, convenient persistence ever adds to assimilable architectures.



Read more about license conditions at www.resoa.org.