Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
They are categorized into these groups according to their functionality:
Group | Description |
---|---|
Control units are used to store input events under controlled settings, such as time delays, before firing them out. | |
Core units transform core values of input events to leave only events that satisfy a given predicate, such as filtering or merging. | |
Data units keep events in memory while performing a sequence of actions to enrich or update the data before firing them through the output ports. | |
Database (DB) units read events from or stores events in supported databases. | |
Devo units send or receive events based on specific queries ran on Devo. The queries can be used in Devo or compatible services. | |
Event units process events according to configured criteria, such as to transform or fire them. | |
HTTP units send HTTP requests to a configurable endpoint. | |
MQ units convert events to records that can be sent to or received from message broker queues. | |
Process units control the process of a Flow. | |
Text units parse, query, or format a text using its supported program. | |
Sink units send events to a configurable channel, such as email or a messaging application. | |
Window units keep events in memory, waiting for a specified condition to be met before sending them through the output ports. |