Node

link GraphQL Schema definition

link Require by

• AlertEmitterNodeEmits alert messages. One per Tenant, automatically created when the Tenant is created.
• AppChangeReceiverNodeReceives change messages from the AppChangeRouterNode. One per App, created when the App is created.
• AppChangeRouterNodeRoutes change messages to the appropriate App. One per Tenant, automatically created when the Tenant is created.
• AuditEmitterNodeEmits audit messages. One per Tenant, automatically created when the Tenant is created.
• BitmapRouterNodeBitMapRouterNodes use a bitmapper function (either inline or referenced) to construct a bitmap of truthy values for each message processed. The message bitmap is then and'ed with route bitmaps. If the result of the and is equal to the route bitmap then the message is sent along that route.
• ChangeEmitterNodeEmits change messages. One per Tenant, automatically created when the Tenant is created.
• CrossTenantReceivingNodeCreated automatically when the other Tenant's CrossTenantSendingApp has a CrossTenantSendingNode created in it. One per CrossTenantSendingNode.
• CrossTenantSendingNodeAllows for sending messages to another Tenant.
• DeadLetterEmitterNodeEmits dead letters (i.e. - undeliverable messages). One per Tenant, automatically created when the Tenant is created.
• EdgeTransmits messages between Nodes.
• ExternalNodeA Node that exists outside the EchoStream Cloud. Can be part of an ExternalApp or CrossAccountApp.
• FilesDotComWebhookNode
• LoadBalancerNodeLoad balances received messages across all sendEdges by distributing messages evenly and then randomly distributing any remaining messages. While not required, all Nodes that are targets to a LoadBalancerNode's sendEdges should be clones of each other. By definition will eliminate guaranteed ordering.
• LogEmitterNodeEmits log messages created by various Node types. One per Tenant, automatically created when the Tenant is created.
• ManagedNodeRepresents a ManagedNode. ManagedNodes are instances of Docker containers that exist within ManagedApps.
• NodeResultA (possibly) paginated result set.
• ProcessorNodeProcessorNodes allow for almost any processing of messages, including transformation, augmentation, generation, combination and splitting.
• QueryRoot Query
• TimerNodeTimerNodes emit echo.timer messages on a time period defined by the scheduleExpression. They can be used to cause other Nodes (normally ProcessorNodes) to perform complex actions on a schedule (e.g. - polling an API every 15 minutes).
• WebhookNodeWebhookNodes allow for receiving of WebHooks from external senders in any JSON mime type. These messages are emitted as-is by the WebHookNode for further processing.
• WebSubHubNodeWebSubHubNodes implement the W3C WebSub Hub feature. They accept echo.websub messages that contain content that requires publishing to subscribers.
• WebSubSubscriptionNode