VLDB 2026 Research / reviewers in the wild / expert
Alexander Benn
dblp:76/7451
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2009
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 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.
| Software engineering, system software, and programming languages
1 paper |
Concurrent programming · 67% Operating systems · 33% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Storage systems · 100% |
Topics — the 4 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Concurrent programming
atomicity |
0.1 | 1 | 2009 | Operating systems transactions · SOSP 2009 |
Concurrent programming
concurrency control |
0.1 | 1 | 2009 | Operating systems transactions · SOSP 2009 |
Storage systems
crash consistency |
0.0 | 1 | 2009 | Operating systems transactions · SOSP 2009 |
Storage systems
file systems |
0.0 | 1 | 2009 | Operating systems transactions · SOSP 2009 |
Methods — techniques the papers use, named apart from their topics
ACID transactions · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2009 | Operating systems transactionsabstractApplications must be able to synchronize accesses to operating system resources in order to ensure correctness in the face of concurrency and system failures. System transactions allow the programmer to specify updates to heterogeneous system resources with the OS guaranteeing atomicity, consistency, isolation, and durability (ACID). System transactions efficiently and cleanly solve persistent concurrency problems that are difficult to address with other techniques. For example, system transactions eliminate security vulnerabilities in the file system that are caused by time-of-check-to-time-of-use (TOCTTOU) race conditions. System transactions enable an unsuccessful software installation to roll back without disturbing concurrent, independent updates to the file system. Donald E. Porter, Owen S. Hofmann, Christopher J. Rossbach, Alexander Benn, Emmett Witchel |
SOSP | 4 |