Graph
Apache Flink

🌊Apache Flink

NEW

Also known as: Flink

A framework and distributed processing engine for stateful computations over unbounded and bounded data streams.

DESCRIPTION

Apache Flink provides low-latency, high-throughput stream processing with robust state management. It supports event-time processing, watermarks, exactly-once state consistency, and fault tolerance via checkpoints and savepoints. Flink’s APIs (DataStream, Table/SQL) serve both streaming and batch use cases. Integrations include Kafka, filesystems, and JDBC sinks. Flink’s runtime scales horizontally and leverages RocksDB for large state. It powers streaming analytics, ETL, CEP, and real-time ML feature pipelines.

ALTERNATIVE DEFINITIONS

Apache Flink is a framework and distributed processing engine for stateful computations over unbounded and bounded data streams.

Highlights both unbounded and bounded processing with stateful computations.

Source

Ververica

Apache Flink is a stream processing framework for high-performance, scalable, and accurate real-time applications.

Emphasizes real-time, performance, and accuracy aspects.

Source

Stateful Processing Event Time Watermark Checkpointing Savepoint Exactly-Once Semantics Apache Kafka Apache Beam RocksDB

COMPETING TERMS

Apache Spark Structured Streaming Kafka Streams

KNOWLEDGE AREAS

Real-time & Streaming Data Data Engineering Platform & Tooling MLOps

TARGET AUDIENCE

Data Engineer MLOps Engineer Software Developer AI Engineer Data Architect

EXTERNAL SOURCES

TOP QUESTIONS

Flink is stream-first with event-time semantics, stateful processing, and low latency, while also supporting batch as a special case.

Category: Concept

Flink uses asynchronous checkpoints and exactly-once state consistency; jobs can resume from savepoints.

Category: Design

For complex event-time logic, large state, and very low latency, Flink is often preferred.

Category: Opinion

Watermarks track event-time progress to handle out-of-order events and trigger computations.

Category: Example

Yes, Flink SQL and the Table API support streaming and batch SQL with time semantics.

Category: Features

State can be very large by leveraging RocksDB state backend and incremental checkpoints.

Category: Performance

Under-provisioned checkpoint storage, insufficient backpressure handling, and ignoring state TTLs cause instability.

Category: Mistakes

Use the quickstart in docs, run a local cluster, and build a simple Kafka-to-sink streaming job.

Category: Getting Started

Through coordinated checkpoints and two-phase commit sinks that ensure state and sink consistency.

Category: Requirements