EDBT 2026 Demo / reviewers in the wild / expert
Kaya Bekiroglu
dblp:135/4669
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2013
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Databases, data mining, and information retrieval
1 paper |
Data stream processing · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 100% |
Topics — the 4 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Data stream processing
fault tolerance |
0.2 | 1 | 2013 | MillWheel: Fault-Tolerant Stream Processing at Internet Scale · Proc. VLDB Endow. 2013 |
Data stream processing › stream processing systems
low-latency stream processing |
0.2 | 1 | 2013 | MillWheel: Fault-Tolerant Stream Processing at Internet Scale · Proc. VLDB Endow. 2013 |
Distributed systems › fault tolerance
exactly-once processing |
0.2 | 1 | 2013 | MillWheel: Fault-Tolerant Stream Processing at Internet Scale · Proc. VLDB Endow. 2013 |
Distributed systems
fault tolerance |
0.2 | 1 | 2013 | MillWheel: Fault-Tolerant Stream Processing at Internet Scale · Proc. VLDB Endow. 2013 |
Methods — techniques the papers use, named apart from their topics
persistent state management · 0.3directed computation graph · 0.3
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2013 | MillWheel: Fault-Tolerant Stream Processing at Internet ScaleabstractMillWheel is a framework for building low-latency data-processing applications that is widely used at Google. Users specify a directed computation graph and application code for individual nodes, and the system manages persistent state and the continuous flow of records, all within the envelope of the framework's fault-tolerance guarantees. This paper describes MillWheel's programming model as well as its implementation. The case study of a continuous anomaly detector in use at Google serves to motivate how many of MillWheel's features are used. MillWheel's programming model provides a notion of logical time, making it simple to write time-based aggregations. MillWheel was designed from the outset with fault tolerance and scalability in mind. In practice, we find that MillWheel's unique combination of scalability, fault tolerance, and a versatile programming model lends itself to a wide variety of problems at Google. Tyler Akidau, Alex Balikov, Kaya Bekiroglu, Slava Chernyak, Josh Haberman, Reuven Lax, Sam McVeety, Daniel Mills, Paul Nordstrom, Sam Whittle |
Proc. VLDB Endow. | 3 |