VLDB 2026 Research / reviewers in the wild / expert
Wilhelm Stannat
dblp:02/619
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2008
0000-0002-0514-3874ORCID · verified
Domains — the database's venue-derived domains; a paper can count in several
Computer networks · 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.
| 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 |
|---|---|---|---|---|
Distributed systems › replication
replica management |
0.1 | 1 | 2008 | Maintaining replicas in unstructured P2P systems · CoNEXT 2008 |
Distributed systems
replication |
0.1 | 1 | 2008 | Maintaining replicas in unstructured P2P systems · CoNEXT 2008 |
Distributed systems › peer-to-peer systems › churn
churn resilience |
0.0 | 1 | 2008 | Maintaining replicas in unstructured P2P systems · CoNEXT 2008 |
Distributed systems
fault tolerance |
0.0 | 1 | 2008 | Maintaining replicas in unstructured P2P systems · CoNEXT 2008 |
Distributed systems
peer-to-peer systems |
0.0 | 1 | 2008 | Maintaining replicas in unstructured P2P systems · CoNEXT 2008 |
Distributed systems › peer-to-peer systems
unstructured overlay |
0.0 | 1 | 2008 | Maintaining replicas in unstructured P2P systems · CoNEXT 2008 |
Methods — techniques the papers use, named apart from their topics
simulation · 0.1probabilistic algorithm · 0.1formal proof · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2008 | Maintaining replicas in unstructured P2P systemsabstractReplication is widely used in unstructured peer-to-peer systems to improve search or achieve availability. We identify and solve a subclass of replication problems where each object is associated with a maintainer node, and its replicas should only be available as long as its maintainer is part of the network. Such requirement can be found in various applications, e.g., when objects are directory lists, service lists, or subscriptions of a publish/subscribe system. We provide maintainers with proven guarantees on the number of replicas, in spite of network churn and crash failures. We also tackle the related problems of changing the number of replicas, updating replicas, balancing storage load in a heterogeneous network, and eliminating replicas left by crashing maintainers. Our algorithm is based on probabilistic methods and is simple to implement. We show by simulation and formal proof that our algorithm is correct. 1. Christof Leng, Wesley W. Terpstra, Bettina Kemme, Wilhelm Stannat, Alejandro P. Buchmann |
CoNEXT | 4 |