Internal Nodes

Internal Nodes are created inside the EchoStream Cloud for your Tenant and are generally implemented as AWS Lambda functions. Using AWS Lambda functions as the execution platform for your Tenant's Internal Nodes provides the following benefits:

• Event-driven processing throughout your tenant, resulting in greater responsiveness.
• Almost unlimited scalability, with an "instance" of your Node running per receiving Edge.
• Extreme resilience for Node processing, as errors in a Node only affect that particular Node execution.
• On-demand processing and billing.

There are two general catgories of Internal Nodes; System Nodes and Tenant Nodes.

System Nodes

System Nodes are created for you by EchoStream when you create your Tenant. They are used by EchoStream and by you to manage your Tenant. You may attach Edges to these Nodes, but you may not create them yourself, delete them, or alter them in any fashion.

The following Nodes fall into this catagory:

• Alert Emitter
• App Change Router
• Audit Emitter
• Change Emitter
• Dead Letter Emitter
• Log Emitter

Tenant Nodes

Tenant Nodes are Nodes that you can create, delete and configure to engineer your Tenant's processing network.

The following Nodes fall into this category:

• Bitmap Router
• Cross Tenant
• Files.com Webhook
• Load Balancer
• Processor
• Timer
• Webhook

Packages provided to Nodes that use Functions

Bitmap Router, Processor and Webhook Nodes all take inline or managed fucntions to allow for customization of their capabilties. The following Python packages are provided to all of these Nodes, and therefore do not have to be included in Message Type, Function or Node requirements.