Demo Data from EDBT 2026 / reviewers in the wild / expert
Dimitri Tombroff
dblp:94/2724
· DBLP profile ↗
4ranked-venue papers
0as first author
2since 2021 · last 2024
0009-0005-4446-539XORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 4 · 2 since 2021Artificial intelligence and machine learning · 1 · 1 since 2021Applied, interdisciplinary, general and emerging computing · 1 · 1 since 2021
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
2 papers |
Transaction processing and concurrency control · 78% Database theory · 22% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 100% |
Topics — the 6 heaviest of 6, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Database theory › integrity constraints
integrity constraint checking |
0.0 | 1 | 1997 | Using Versions in Update Transactions: Application to Integrity Checking · VLDB 1997 |
Transaction processing and concurrency control › update management
update transaction |
0.0 | 1 | 1997 | Using Versions in Update Transactions: Application to Integrity Checking · VLDB 1997 |
Transaction processing and concurrency control › recovery
crash recovery |
0.0 | 1 | 1996 | DSDT: Durable Scripts Containing Database Transactions · ICDE 1996 |
Transaction processing and concurrency control › transaction models
extended transaction models |
0.0 | 1 | 1996 | DSDT: Durable Scripts Containing Database Transactions · ICDE 1996 |
Transaction processing and concurrency control › recovery
log-based recovery |
0.0 | 1 | 1996 | DSDT: Durable Scripts Containing Database Transactions · ICDE 1996 |
Distributed systems
fault tolerance |
0.0 | 1 | 1996 | DSDT: Durable Scripts Containing Database Transactions · ICDE 1996 |
Methods — techniques the papers use, named apart from their topics
transactional remote procedure calls · 0.0logging · 0.0compensation · 0.0checkpoints · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | WebAssembly serverless join: A Study of its ApplicationabstractInternational audience Chanattan Sok, Laurent d'Orazio, Reyyan Tekin, Dimitri Tombroff |
SSDBM | 4 |
| 2022 | The Lannion report on Big Data and Security Monitoring ResearchabstractDuring the last decade, big data management has attracted increasing interest from both the industrial and academic communities. In parallel, Cyber Security has become mandatory due to various and more intensive threats. In June 2022, a group of researchers has met to reflect on their community’s impacts on current research challenges. In particular, they have considered four dimensions: (1) dedicated systems being data processing and analytic platforms or time series management systems; (2) graphs analytics and distributed computation; (3) privacy; and (4) new hardware. Laurent d'Orazio, Jalil Boukhobza, Omer F. Rana, Juba Agoun, Le Gruenwald, Hervé Rannou, Elisa Bertino, Mohand-Said Hacid, Taofik Saïdi, Georges Bossert, Dimitri Tombroff, Makoto Onizuka |
IEEE Big Data | 12 |
| 1997 | Using Versions in Update Transactions: Application to Integrity Checking
François Llirbat, Eric Simon, Dimitri Tombroff |
VLDB | 3 |
| 1996 | DSDT: Durable Scripts Containing Database TransactionsabstractDSDT is a proposed method for creating durable scripts which contain short ACID transactions as components. Workflow scripts are an example. The context of the script is made durable by writing a log record whenever an event occurs which cannot be replayed. Log checkpoints are used to minimize the recovery time. DSDT can be written in stand-alone mode, communicating with a DBMS by transactional remote procedure calls and maintaining its own logging system, or it can be made part of a DBMS by modifying the DBMS transaction manager source code. DSDT provides a panic button (signal-exit) and the ability to specify what action should be taken on restart after a system failure. The programmer can also specify actions, such as "compensation" transactions, to be taken after another signal (signal-cancel) arrives. DSDT enables most extended transaction models to be expressed in scripts modulo the guarantees of compensation. Recovery after system failure is shown to be correct. Betty Salzberg, Dimitri Tombroff |
ICDE | 2 |