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:

• ResoaNodeGateway: Nodes act as a container for Resoa service implementations. You can deploy services (jarDomains) on several nodes, Resoa will ensure that all nodes, providing the same domain, are linked by a resoa stack managed connection.
• ResoaControllerGateway: Controllers manage the Resoa topology by holding a stack connection to each running component. They act as a service container too, please deploy the Resoa internal services (implemented within the package org.resoa.topology.service) only. At least one Controller must run inside the grid, otherwise a node will not receive any deployment information on start up. A controller crash during runtime does not affect the grid service availability, all nodes still will reply to incoming requests, only the central RestSession management will be not available. Controller nodes can re-join the grid at any time, they simply try to establish a connection to all components, specified within the topology configuration.
• RestGateway: RestGateways do not host any resoa services, they use a stack connection for service invocation. They identify the nodes, they need to connect to, by examining the ResoaInfo record, transmitted by a controller after start up. The node project only provides a basic RestGateway implementation, look to the org.resoa.rest.RestServer (implemented within resoa.rest project), this class extends the RestGateway and acts as a fully webserver integrated into Resoa architecture.

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.