On behalf of the team, I am pleased to announce several releases in the Spring Cloud Stream and Spring Cloud Data Flow family of projects.
Spring Cloud Stream 1.0 M3 introduces the following features
- Many improvements in middleware binding. In particular for supporting multiple binders, so you can now have RabbitMQ as an input and Kafka be the output, for example.
- Partitioning improvements
Spring Cloud Stream Modules 1.0 M2 adds many new modules with updated documentation.
- Sources: File, Load Generator, sftp, and tcp
- Processors: httpclient, PMML, and Splitter
- Sinks: Cassandra, Field Value Counter, file, ftp, gemfire, HDFS Dataset, JDBC, tcp, throughput, and websocket
Spring Cloud Data Flow 1.0 M2 has split out the multiple Admin Server implementations into separate github repositories. The Spring Cloud Data Flow core project supports deploying modules on a local host in separate JVMs
The following Data Flow implementations were also released
- Data Flow Apache YARN 1.0 M1
- Data Flow Cloud Foundry 1.0 M1
- Data Flow Apache Mesos 1.0 M1
- Data Flow Kubernetes 1.0 M1
- The Admin UI is available across all Admin implementations.
- The Admin UI adds a new Runtime Modules tab that allows you to remotely monitor and manage deployed modules.
- Flo for Spring Cloud Data Flow 1.0 M1 is now available with drag-and-drop support for creating Streams.
There is also a new Data Flow Samples repository to collect some common use-cases, and look forward to a blog post on how to get started on creating your own custom modules and deploying them in Spring Cloud Data Flow.
Of note, we are using github issues with waffle.io for issue management. Links to the waffle boards are on each project’s github page. You can find the links to each github project page under the main Spring Cloud Data Flow project page.