• v7.1.0
    • v7.11.0 (latest)
    • v7.10.0
    • v7.9.0
    • v7.8.0
    • v7.7.0
    • v7.6.0
    • v7.5.0
    • v7.3.0
    • v7.2.0
    • v7.1.1
    • v7.1.0
    • v7.0.8
  • Services & Support
  • Devo.com
  • Contact
    • Contact Us
    • Request a Demo
    • Partner Inquiry
  • Log In
    • USA Devo
    • EU Devo
PREVIOUS
Modify your Flow layout
NEXT
Control

Flow / Unit types

Download as PDF

Unit types

Units are the main elements of Devo Flow, and can be classified under three general groups:

Sources

These units get input data from different repositories, servers, etc. or generate events on their own. For example, you can use the DevoSource unit to read events from a Devo query or generate events automatically with a specific frequency using the Generator unit.

Processors

These units transform the events sent by the source element. For example, you can transform an event that contains a list into a sequence of its different elements using the Detacher unit, or parse a properly formated JSON using the JsonParser unit.

Sinks

These units send output events to different external repositories, sinks, etc. For example, you can send your events to a Slack channel using the SlackSink unit, or store them in a Neo4j database using the Neo4jSink unit.

The panel at the left area of Devo Flow groups events under more specific categories according to the type of function they perform. The following sections include all the available units in the tool and describe what they do and their available input/output ports. 

They are categorized into these groups according to their functionality:

GroupDescription
ControlControl units are used to store input events under controlled settings, such as time delays, before firing them out.
CoreCore units transform core values of input events to leave only events that satisfy a given predicate, such as filtering or merging.
DataData units keep events in memory while performing a sequence of actions to enrich or update the data before firing them through the output ports.
DBDatabase (DB) units read events from or stores events in supported databases.
DevoDevo units send or receive events based on specific queries ran on Devo. The queries can be used in Devo or compatible services.
EventEvent units process events according to configured criteria, such as to transform or fire them.
HTTPHTTP units send HTTP requests to a configurable endpoint.
MQMQ units convert events to records that can be sent to or received from message broker queues.
TextText units parse, query, or format a text using its supported program.
SinkSink units send events to a configurable channel, such as email or a messaging application.
WindowWindow units keep events in memory, waiting for a specified condition to be met before sending them through the output ports.
Download as PDF

PREVIOUS
Modify your Flow layout
NEXT
Control

Export

See what Devo can do for you. Request a demo!
Discover what's new (Release notes)
  • v7.1.0
    • v7.11.0 (latest)
    • v7.10.0
    • v7.9.0
    • v7.8.0
    • v7.7.0
    • v7.6.0
    • v7.5.0
    • v7.3.0
    • v7.2.0
    • v7.1.1
    • v7.1.0
    • v7.0.8
  • Services & Support
  • Devo.com
  • Contact
    • Contact Us
    • Request a Demo
    • Partner Inquiry
  • Log In
    • USA Devo
    • EU Devo
  • +1 888 6830910 (USA)
  • +34 900 838 880 (Spain)
Copyright © 2019 Legal Terms Privacy Policy Cookies Policy

Powered by Confluence and Scroll Viewport