Companies running Apache Flink in production include Netflix, which runs more than 30,000 Flink jobs across ad tech, recommendations, and a real-time distributed graph, evolved out of Keystone, its original stream processing platform. This page indexes production Apache Flink use cases, starting with Netflix’s own architecture and growing as we research and publish more.
Apache Flink use cases
Netflix
Netflix runs Apache Flink at large scale for stream processing as a service (Keystone), a real-time distributed graph connecting member activity across services, SQL-based stream transformations (the Data Mesh SQL Processor), and real-time replacements for batch metrics such as take fraction. Sourced from Netflix’s own engineering blog and conference talks by named Netflix engineers.
FAQ
What companies use Apache Flink in production?
Netflix runs Apache Flink at large scale, with more than 30,000 jobs spanning a self-serve stream processing platform, a real-time distributed graph, and SQL-based stream transformations, as detailed in our own use-case writeup on Netflix. We are adding further named production deployments to this page as we research and publish them.
What is Apache Flink used for?
Apache Flink is used for stateful, low-latency stream processing: enrichment, joins across streams, event-time windowing, and continuous SQL over unbounded data, typically fed by a system like Apache Kafka.