Pre-packaged Applications (3.x)

This page contains information about the 3.x release stream-applications which introduces many new features and some changes which are incompatible with the 2.x release. If you are looking for information about the 2.x release, see pre-packaged applicattions.

The Spring team provides and supports a selection of pre-packaged applications used to assemble various data integration and processing pipelines and to support Spring Cloud Data Flow development, learning and experimentation.

Getting Started

If you are interested in upgrading existing data pipelines to use 3.x applications, see the Migration Guide.

All pre-packaged streaming applications:

  • Are available as Apache Maven artifacts or Docker images
  • Use RabbitMQ or Apache Kafka
  • Support monitoring through Prometheus and InfluxDB
  • Contain metadata for application properties used in the UI and code completion in the shell

You can register stream and task applications by using the Data Flow UI or the shell.

You can register applications individually by using the app register command or in bulk by using the app import command.

For streams, depending on whether you use Kafka or RabbitMQ, you can register the applications by using the respective URLs:

Using the Data Flow UI, these links are included for pre-fill:

Bulk register applications

From the Data Flow Shell, you can bulk import and register the applications, as the following example shows:

dataflow:>app import --uri

Stream Applications

The Spring team develops and maintains stream applications and publishes these applications to the Spring public Maven repository and to Dockerhub in accordance with a release schedule, normally following significant Spring Boot or Spring Cloud Stream releases. The pre-packaged stream applications are Spring Boot executable jars that are built with a specific binder implementation. For each stream app, we provide separate exacutable applications for RabbitMQ and Kafka.

Currently available stream applications include:

Source Processor Sink
cdc-debezium aggregator cassandra
file bridge analytics
ftp filter wavefront
geode groovy file
http header-enricher ftp
jdbc http-request geode
jms image-recognition jdbc
load-generator object-detection log
mail semantic-segmentation mongodb
mongodb script mqtt
mqtt splitter pgcopy
rabbit transform rabbit
s3 twitter-trend redis
sftp router
syslog rsocket
tcp s3
time sftp
twitter-message tasklauncher
twitter-search tcp
twitter-stream throughput
websocket twitter-message

Bulk Registration of Stream Applications

Spring Cloud Data Flow supports bulk registration of applications, via a standard properties file format. For convenience, we publish static properties files with application-URIs (for either maven or docker) for all the out-of-the-box stream and task/batch apps. You can use these files in Spring Cloud Data Flow to register all the application-URIs in bulk. Alternately, you can register them individually or provide your own custom property file with only the required application-URIs in it. Bulk registration is convenient for getting started with SCDF. To reduce clutter, it is recommended, to maintain a “focused” list of desired application-URIs in a custom property file.