Cloud Native Dataflow Orchestration
Cloud Native Dataflow Orchestration
The video below will provide an overview of the Spring Cloud Data Flow architecture–including how it evolved out of Spring XD. Additionally, a streaming application will be deployed on each of the supported runtimes in a live demo.
Join the DZone community and get the full member experience.
Join For FreeDiscover a centralized approach to monitor your virtual infrastructure, on-premise IT environment, and cloud infrastructure – all on a single platform.
Recorded at SpringOne2GX 2015.
Speakers: Mark Fisher & Patrick Peralta
Big Data Track
Slides: http://www.slideshare.net/SpringCentral/cloud-native-data-flow-orchestration
The Spring Cloud Stream and Spring Cloud Task projects provide a simple and powerful framework for creating cloud-native data microservices for stream and batch processing. Each microservice in these distributed systems consists of a stand-alone Spring Boot application.
While it is possible to define data pipelines across these microservice apps manually, Spring Cloud Data Flow is an integrated orchestration layer that provides a highly productive deployment and management experience for development and ops. Streams and tasks are defined using the same DSL and shell/UI introduced with Spring XD. Furthermore, a pluggable runtime SPI allows Spring Cloud Data Flow to coordinate these applications across a variety of distributed runtime platforms including Apache YARN, Lattice, and Cloud Foundry.
This session will provide an overview of the Spring Cloud Data Flow architecture–including how it evolved out of Spring XD. Additionally, a streaming application will be deployed on each of the supported runtimes in a live demo.
Learn how to auto-discover your containers and monitor their performance, capture Docker host and container metrics to allocate host resources, and provision containers.
Like This Article? Read More From DZone
Published at DZone with permission of Pieter Humphrey , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}