Demo Data from VLDB 2026 / reviewers in the wild / expert
M. Leszak
dblp:80/5547
· DBLP profile ↗
3ranked-venue papers
2as first author
0since 2021 · last 1991
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 2 · 1 first-authorSoftware engineering, systems software and programming languages · 1 · 1 first-author
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.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Distributed systems › distributed database › commit protocol
distributed commit |
0.0 | 1 | 1982 | A Distributed Transaction Processing Protocol Based on Majority Consensus · PODC 1982 |
Distributed systems
fault tolerance |
0.0 | 1 | 1982 | A Distributed Transaction Processing Protocol Based on Majority Consensus · PODC 1982 |
Distributed systems › consensus › fault-tolerant consensus
majority consensus |
0.0 | 1 | 1982 | A Distributed Transaction Processing Protocol Based on Majority Consensus · PODC 1982 |
Distributed systems
transaction processing |
0.0 | 1 | 1982 | A Distributed Transaction Processing Protocol Based on Majority Consensus · PODC 1982 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1991 | Integration Strukturierter Methoden zur Anforderungsspezifikation von Informationssystemen
M. Leszak, B. Franzen, K. Fritschi |
Requirements Engineering | 1 |
| 1982 | A Fault-Tolerant Scheme for distributed transaction commitment
M. Leszak, Helmut Breitwieser |
ICDCS | 1 |
| 1982 | A Distributed Transaction Processing Protocol Based on Majority ConsensusabstractAn n-failure-resilient protocol for distributed transaction processing regarding site crash, network partitioning, and local failures like abort of subtransactions is specified. The three-phased protocol contains concurrency control, a mechanism enforcing mutual consistency, and commitment based on majority consensus w.r.t. multiple copies of entities. To cope with transaction manager failures, backup processes for the manager are used. Data redundancy given by multiple copies in a partially redundant database is utilized to improve the resiliency of the protocol, i.e. to improve especially the successful commitment of update transactions processed by the protocol. The protocol is n-failure-resilient if the least redundant entity to be accessed by a transaction is mapped onto at least 2n+1 file copies in the distributed database. Helmut Breitwieser, M. Leszak |
PODC | 2 |