Cloudera's Data-in-Motion vision
summary
Cloudera integrates Apache Flink into its hybrid cloud platform, committing to core streaming API support in December and a private beta launching next week. Ingestion uses Apache NiFi at the edge into Kafka topics, with cleaning, a Schema Registry connector, Streams Messaging Manager, and enterprise bits (Ranger, Atlas, Knox). Customers run telecom pipelines ingesting millions of messages a second, manufacturing use cases aim to avoid line losses costing $20,000 a minute, and healthcare uses low-latency EHR updates; contributions and connectors return to open source.
AI-written summary · about
chapters (14)
- 0:00Introduction to vision
- 1:10Evolution of streaming platforms
- 3:19Customer demand for Flink
- 5:04Telecom and banking use cases
- 7:12Healthcare streaming challenges
- 8:58High-tech manufacturing IoT
- 10:44Natural resources telemetry
- 12:52Tracking use case blueprint
- 13:34Edge device data ingestion
- 15:48Cloudera’s Flink integration plans
- 18:14Enterprise features and security
- 19:59Community collaboration and resources
- 20:40Flink team and beta program
- 22:02Next sessions and closing
related talks
29mA brief history of time with Apache Flink
35mKeynote: Stream analytics made real with Pravega and Apache Flink
34mKeynote | Flink Ahead 2.0: The Sequel
26mArchitecting real-time transactional data lake
20mBuilding realtime efficient queries in an IOT platform
42mHow Netflix Built a Real-Time Distributed Graph for Internet Scale
30mReal-Time Data Ingestions for Data Fabric and AI Applications
29mThe need for speed: Data streaming architectures