Demo Data from VLDB 2026 / reviewers in the wild / expert
Marcus Jager
dblp:95/563
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2008
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 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 · 87% Storage systems · 13% |
Topics — the 6 heaviest of 7, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Distributed systems
consensus |
0.1 | 1 | 2008 | Niobe: A practical replication protocol · ACM Trans. Storage 2008 |
Distributed systems › consistency models
consistency guarantees |
0.1 | 1 | 2008 | Niobe: A practical replication protocol · ACM Trans. Storage 2008 |
Distributed systems › replication
primary-backup replication |
0.1 | 1 | 2008 | Niobe: A practical replication protocol · ACM Trans. Storage 2008 |
Distributed systems
replication |
0.1 | 1 | 2008 | Niobe: A practical replication protocol · ACM Trans. Storage 2008 |
Storage systems
distributed storage |
0.0 | 1 | 2008 | Niobe: A practical replication protocol · ACM Trans. Storage 2008 |
Storage systems › storage architecture
enterprise storage |
0.0 | 1 | 2008 | Niobe: A practical replication protocol · ACM Trans. Storage 2008 |
Methods — techniques the papers use, named apart from their topics
formal verification · 0.1TLA+ specification · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2008 | Niobe: A practical replication protocolabstractThe task of consistently and reliably replicating data is fundamental in distributed systems, and numerous existing protocols are able to achieve such replication efficiently. When called on to build a large-scale enterprise storage system with built-in replication, we were therefore surprised to discover that no existing protocols met our requirements. As a result, we designed and deployed a new replication protocol called Niobe . Niobe is in the primary-backup family of protocols, and shares many similarities with other protocols in this family. But we believe Niobe is significantly more practical for large-scale enterprise storage than previously published protocols. In particular, Niobe is simple, flexible, has rigorously proven yet simply stated consistency guarantees, and exhibits excellent performance. Niobe has been deployed as the backend for a commercial Internet service; its consistency properties have been proved formally from first principles, and further verified using the TLA + specification language. We describe the protocol itself, the system built to deploy it, and some of our experiences in doing so. John MacCormick, Chandramohan A. Thekkath, Marcus Jager, Kristof Roomp, Lidong Zhou, Ryan S. Peterson |
ACM Trans. Storage | 3 |