The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
State management in Apache Flink®: consistent stateful distributed stream processing
Abstract
Stream processors are emerging in industry as an apparatus that drives analytical but also mission critical services handling the core of persistent application logic. Thus, apart from scalability and low-latency, a rising system need is first-class support for application state together with strong consistency guarantees, and adaptivity to cluster reconfigurations, software patches and partial failures. Although prior systems research has addressed some of these specific problems, the practical challenge lies on how such guarantees can be materialized in a transparent, non-intrusive manner that relieves the user from unnecessary constraints. Such needs served as the main design principles of state management in Apache Flink, an open source, scalable stream processor. We present Flink's core pipelined, in-flight mechanism which guarantees the creation of lightweight, consistent, distributed snapshots of application state, progressively, without impacting continuous execution. Consistent snapshots cover all needs for system reconfiguration, fault tolerance and version management through coarse grained rollback recovery. Application state is declared explicitly to the system, allowing efficient partitioning and transparent commits to persistent storage. We further present Flink's backend implementations and mechanisms for high availability, external state queries and output commit. Finally, we demonstrate how these mechanisms behave in practice with metrics and large-deployment insights exhibiting the low performance trade-offs of our approach and the general benefits of exploiting asynchrony in continuous, yet sustainable system deployments.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Apache Flink offers one of the most elaborated dataflow models, providing precise control of time and state.
“It offers one of the most elaborated dataflow models, providing precise control of time and state (Carbone et al., 2015(Carbone et al., , 2017;;Akidau et al., 2021).”
From Benchmarking scalability of stream processing frameworks deployed as microservices in the cloud (2024) · cites this paper as Carbone et al., 2017
Citations
Cites
A catalog of stream processing optimizations
Hirzel, M., Soulé, R., Schneider, S., Gedik, B., & Grimm, R. (2014) · ACM Computing Surveys · doi:10.1145/2528412 · Cited by 299
Flagged first, then by citations
Research works printed but not linked: 41
- Spark's Structured Streaming Introduction, 2016, https://www.oreilly.com/learning/apache-spark-2-0--introduction-to-structured-streaming
- Rbea, 2016, Scalable Real-Time Analytics at King. https://techblog.king.com/rbea-scalable-real-time-analytics-king/
- Apex Apache, 2017, https://apex.apache.org
- Beam Apache, 2017, https://beam.apache.org/
- Flink Apache, 2017, http://flink.apache.org/
- Storm Apache, 2017, http://storm.apache.org/
- Forward Flink, 2017, http://flink-forward.org/
- Dataflow Google Cloud, 2017, https://cloud.google.com/dataflow/
- Kafka, 2017, http://2016.flink-forward.org/kb_sessions/a-brief-history-of-time-with-apache-flink-real-time-monitoring-and-analysis-with-flink-kafka-hb/
- 2017, http://rocksdb.org/
- Netflix Stream, 2017, http://sf.flink-forward.org/kb_sessions/keynote-stream-processing-with-flink-at-netflix/
- Stream Processing Programming Model The Trident, 2017, http://storm.apache.org/releases/0.10.0/Trident-tutorial.html
- 10.1007/s00778-003-0095-z · DOI
- 10.14778/2536222.2536229 · DOI
- 10.14778/2824032.2824076 · DOI · Paper page
- 10.1007/s00778-014-0357-y · DOI
- Arasu A., 2004, Stream: The stanford data stream management system. Book chapter
- 10.1145/1807128.1807148 · DOI
- Carbone P., 2015, IEEE Data Engineering Bulletin, page, 28
- 10.1145/2463676.2465282 · DOI
- 10.1145/1809028.1806638 · DOI
- 10.1145/872757.872857 · DOI
- 10.1145/214451.214456 · DOI
- 10.1145/1365815.1365816 · DOI
- Cherniack M., 2003, Scalable distributed stream processing. In CIDR, 3, 257
- 10.5555/2789272.2789277 · DOI
- 10.1145/1327452.1327492 · DOI · Paper page
- 10.1145/1323293.1294281 · DOI
- 10.1145/568522.568525 · DOI
- 10.1145/1807128.1807139 · DOI
- Hindman B., 2011, NSDI
- Hunt P., 2010, USENIX annual technical conference, 9
- 10.14778/3007263.3007272 · DOI
- Kreps J., 2011, NetDB
- 10.14778/2212351.2212354 · DOI
- Marz N., 2015, Big Data: Principles and best practices of scalable realtime data systems
- 10.1145/2517349.2522738 · DOI
- 10.1145/2523616.2523633 · DOI · Paper page
- 10.1109/IPDPS.2012.108 · DOI
- Zaharia M., 2010, HotCloud
- Zaharia M., 2012, Proceedings of the 4th USENIX conference on Hot Topics in Cloud Ccomputing, 10
Cited by
Sorted by citations
From cloud computing to sky computing
Stoica, I., & Shenker, S. (2021) · Proceedings of the Workshop on Hot Topics in Operating Systems · doi:10.1145/3458336.3465301 · Cited by 89
Benchmarking scalability of stream processing frameworks deployed as microservices in the cloud
Henning, S., & Hasselbring, W. (2024) · Journal of Systems and Software · doi:10.1016/j.jss.2023.111879 · Cited by 85
Metadata
- Authors
- Carbone, P., Ewen, S., Fóra, G., Haridi, S., Richter, S., & Tzoumas, K.
- Affiliations
- KTH Royal Institute of Technology (SE)
- data Artisans
- King Digital Entertainment Limited
- Venue
- Proceedings of the VLDB Endowment
- Published
- 2017-08
- Volume
- 10
- Issue
- 12
- Pages
- 1718-1729
- ISSN
- 2150-8097 (ISSN-L)
- OpenAlex
- W2752238980
- Cited by
- 285
- References
- 1
- Citations by year
- 2026: 42 · 2025: 31 · 2024: 30 · 2023: 26 · 2022: 32 · 2021: 33 · 2020: 27 · 2019: 37 · 2018: 26 · 2017: 1
- FWCI
- 30.81
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Proceedings of the VLDB Endowment (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Advanced Database Systems and Queries
- Physical Sciences › Computer Science › Computer Networks and Communications › Distributed systems and fault tolerance
- Physical Sciences › Computer Science › Information Systems › Cloud Computing and Resource Management
- Keywords
- Apache Flink, state management, stream processing, distributed snapshots, fault tolerance, high availability, checkpointing, pipelined execution, state partitioning, cluster reconfiguration, version control
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review