Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Bernd Walter

dblp:w/BerndWalter · DBLP profile ↗
← Back
11ranked-venue papers
8as first author
0since 2021 · last 2006
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Computer networks · 5 · 5 first-authorDatabases, data management, data science and information retrieval · 4 · 2 first-authorArtificial intelligence and machine learning · 2Systems, architecture and hardware · 2 · 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
4 papers
Distributed systems · 83% Storage systems · 17%
Databases, data mining, and information retrieval
2 papers
Transaction processing and concurrency control · 88% Database system architecture and tuning · 12%

Topics — the 10 heaviest of 11, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Distributed systems
fault tolerance
0.021986
A tuneable protocol for symmetric surveillance in distributed systems · SIGCOMM 1986
Strategies for Handling Transactions in Distributed Data Base Systems During Recovery · VLDB 1980
Distributed systems
distributed database
0.021984
Replicated Data and Stable Storage in Distributed Database Systems · INFOCOM 1984
Using Redundancy for Implementing Low-Cost Read-Only Transactions in a Distributed Database System · INFOCOM 1983
Distributed systems › replication
replicated data
0.021984
Replicated Data and Stable Storage in Distributed Database Systems · INFOCOM 1984
Using Redundancy for Implementing Low-Cost Read-Only Transactions in a Distributed Database System · INFOCOM 1983
Distributed systems › fault tolerance
failure detection
0.011986
A tuneable protocol for symmetric surveillance in distributed systems · SIGCOMM 1986
Storage systems › storage reliability › fault-tolerant storage
stable storage
0.021984
Replicated Data and Stable Storage in Distributed Database Systems · INFOCOM 1984
Using Redundancy for Implementing Low-Cost Read-Only Transactions in a Distributed Database System · INFOCOM 1983
Transaction processing and concurrency control
nested transactions
0.011984
Nested Transactions with Multiple Commit Points: An Approach to the Structuring of Advanced Database Applications · VLDB 1984
Distributed systems › transaction processing
read-only transactions
0.011983
Using Redundancy for Implementing Low-Cost Read-Only Transactions in a Distributed Database System · INFOCOM 1983
Transaction processing and concurrency control
distributed transaction management
0.011980
Strategies for Handling Transactions in Distributed Data Base Systems During Recovery · VLDB 1980
Transaction processing and concurrency control
recovery
0.011980
Strategies for Handling Transactions in Distributed Data Base Systems During Recovery · VLDB 1980
Storage systems
storage reliability
0.011984
Replicated Data and Stable Storage in Distributed Database Systems · INFOCOM 1984

Methods — techniques the papers use, named apart from their topics

protocol design · 0.0formal analysis · 0.0replication · 0.0redundancy · 0.0
YearPublicationVenuePosition
2006 Analysing Social Networks Within Bibliographical Data
Stefan Klink, Patrick Reuther, Alexander Weber 0001, Bernd Walter, Michael Ley
DEXA4
1991 EFTA: A Database Retrieval Algebra for Feature-Terms
Thomas Ludwig 0001, Bernd Walter
Data Knowl. Eng.2
1986 A tuneable protocol for symmetric surveillance in distributed systems
abstract
In distributed systems surveillance protocols are used for monitoring the status of remote sites. A remote site is regarded as being available as long as messages are received from this site, otherwise it is regarded as being unavailable. If a site becomes unavailable, this will be reported to other sites and recovery actions can be initiated. Using an example it will be shown that in certain cases it is necessary, that whenever some site S1 detects the unavailability of some other site S2, within a fixed amount of time S2 must also have detected an unavailability of S1. Unfortunately, this cannot be guaranteed by existing surveillance protocols. Another problem with existing protocols is, that remote sites are usually reported as being unavailable after being timed out only once, i.e. the loss of just one message might cause complete systems to back out.
Bernd Walter
SIGCOMM1
1985 Network Partitioning and Symmetric Surveillance Protocol
Bernd Walter
ICDCS1
1984 Some Thoughts on Communication in Distributed Database Systems
Bernd Walter
ICC (2)1
1984 A Kernel for Transaction Oriented Communication in Distributed Database Systems
Kurt Rothermel, Bernd Walter
ICDCS2
1984 Replicated Data and Stable Storage in Distributed Database Systems
Bernd Walter
INFOCOM1
1984 Nested Transactions with Multiple Commit Points: An Approach to the Structuring of Advanced Database Applications
Bernd Walter
VLDB1
1983 Using Redundancy for Implementing Low-Cost Read-Only Transactions in a Distributed Database System
Bernd Walter
INFOCOM1
1982 A Robust and Efficient Protocol for Checking the Availability of Remote Sites
Bernd Walter
Comput. Networks1
1980 Strategies for Handling Transactions in Distributed Data Base Systems During Recovery
Bernd Walter
VLDB1