Streams

Within Cortex's dynamic, event-driven architecture, Streams serve as the cornerstone, orchestrating the flow of time-sequenced events through a distinct and recognizable Stream Name. Each Stream is a carefully structured entity, complete with a set of Attributesthat defines the structure of the data it encompasses.

Streams Entering and Exiting Cortex

Cortex enables the consumption of external events via Source Nodes and the publishing of processed events through Sink Nodes within Applications.

For Applicationsinteracting with external data sources or sinks, Source Nodes and Sink Nodes require careful configuration across three aspects:

• Source/Sink Type to define the connection method, e.g., HTTP, Email, NATS... (cf.Step 1 - Source Type, Step 1 - Sink Type)

• Attributes to specify data types for each attribute (cf. New Attributes and New Attributes for Source and Sink Nodes; respectively)

• Mapping to detail the data consumption or publishing format (cf. Step 3 - Mapping and Step 3 - Mapping for Source and Sink Nodes; respectively)

Internal Streams with Stream Nodes

Within the Cortex Applications, StreamNodes facilitate the internal routing of events to various Processing Nodes, allowing you to tailor data handling to your specific requirements. (cf. Processing Nodes Cluster)

• You have flexibility to create multiple streams within a single Application, through the deployment of numerous Stream Nodes.

• Within these Stream Nodes, you can create New Attributes, drawing upon data from preceding nodes to enrich and customize the stream further. (cf. Defining New Attributes)

As input streams are already aligned through Source Nodes mappings, there is no need to repetitively define mappings for each Stream Node within your Applications.

This intrinsic mapping ensures a seamless transition of data across Nodes, streamlining the processing and enhancing the overall efficiency of data manipulation within Cortex Applications.