The Flink Runtime | Apache Flink 101

► TRY THIS YOURSELF: https://cnfl.io/apache-flink-101-modu...

This video explains how a Flink cluster is organized and the roles of Job Managers and Task Managers in running your applications.

Flink supports both batch and stream processing. These two execution modes place different demands on the runtime. Understanding these differences is helpful in appreciating what problems the Flink runtime has to solve and why it is organized the way it is.

For a complete IMMERSIVE HANDS-ON EXPERIENCE: https://cnfl.io/apache-flink-101-modu...


--
ABOUT CONFLUENT
Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations. To learn more, please visit www.confluent.io.

#flink #kafka #streamprocessing #confluent

• #science_technology
• #confluent
• #kafka
• #flink
• #apache_flink
• #apache_kafka
• #how_does_flink_work
• #what_is_a_flink_job
• #what_is_flink
• #parallel_processing
• #stream_processing
• #microservices
• #batch_processing
• #flink_vs_kafka
• #flink_sql
• #streaming_data_pipelines
• #data_streaming
• #data_processing
• #flink_task_slots
• #flink_stream_processing
• #streaming_data
• #flink_configuration
• #flink_architecture
• #stream_processing_vs_batch_processing
• #kafka_streams
• #why_flink
• #event_driven
• #confluent_cloud
• #data_in_motion