Nodes

Nodes process messages in your Tenant. This can include processing the message, transforming the message, routing the message, transfering the message and much more.

Node Categories

Node types are grouped into two catagories; Internal Nodes and External Nodes.

Internal Nodes exist within the EchoStream Cloud for your Tenant and are generally implemented as AWS Lambda functions. This allows for almost unlimited scalability, extreme reliability, and on-demand processing.

External Nodes exist outside of the EchoStream Cloud for your Tenant. Their implementation is varied and dependant upon the desires of the implementor (which may be you or a partner that you provide the External Node to). For example, an External Node could be a pod running in Kubernetes, a Docker container running in Docker Swarm, a traditional server process running in a Linux server, or a component of a monolithic application.

Edges, Fan-in and Fan-out

Nodes can receive message, send messages, or both. Messages are received over Edges where the Node is the target of the Edge, and are sent over Edges where the Node is the source of the Edge.

All Nodes within EchoStream can fan-in (receive messages from multiple Edges) if they can receive messages and fan-out (send messages on multiple Edges) if they can send messages.

Message Types

Nodes are only able to process specific Message Types which are set when the Node is created. If the Node can receive messages it will have a receive Message Type. If it can send messages it will have a send Message Type. Message Types cannot be changed after Node creation.

Receive Message Type

The receive Message Type dictates what type of messages that the Node can receive and, by default, the other Nodes in your Tenant that you can connect to it with an Edge.

The Node uses the receive Message Type to

• audit messages that are received over Edges.
• template inline Bitmapper Functions in Bitmapper Router Nodes.
• template inline Processor Functions in Processor Nodes.

If a Node is created without a receive Message Type then it is incapable of receiving messages or being the target of an Edge.

Send Message Type

The send Message Type dictates what type of messages that the Node can send and, by default, the other Nodes in your Tenant that your can connect to it with an Edge.

Some Nodes will use the send Message Type to audit messages that they create. This is often done on Nodes that originate messages into your EchoStream Tenant, such as the Emitter Nodes, and certain Managed Nodes and External Nodes depending on how the Node is coded.

If a Node is created without a send Message Type then it is incapable of sending messages or being the source of an Edge.