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

Gabriel Bracha

dblp:54/4334 · DBLP profile ↗
← Back
8ranked-venue papers
8as first author
0since 2021 · last 1987
0000-0003-4391-864XORCID · corroborated

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

Systems, architecture and hardware · 4 · 4 first-authorTheory of computation · 2 · 2 first-authorApplied, interdisciplinary, general and emerging computing · 2 · 2 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
7 papers
Distributed systems · 95% Cloud and datacenter computing · 5%
Theoretical computer science
5 papers
Distributed computing theory · 100%

Topics — the 18 heaviest of 20, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Distributed systems › fault tolerance
byzantine fault tolerance
0.041987
An O(log n) expected rounds randomized byzantine generals protocol · J. ACM 1987
An O(\mathop lg n) Expected Rounds Randomized Byzantine Generals Protocol · STOC 1985
An Asynchronou [(n-1)/3]-Resilient Consensus Protocol · PODC 1984
Distributed systems
fault tolerance
0.041987
An O(log n) expected rounds randomized byzantine generals protocol · J. ACM 1987
Resilient Consensus Protocols · PODC 1983
Asynchronous Consensus and Broadcast Protocols · J. ACM 1985
Distributed computing theory › consensus
asynchronous consensus
0.021987
Asynchronous Byzantine Agreement Protocols · Inf. Comput. 1987
Asynchronous Consensus and Broadcast Protocols · J. ACM 1985
Distributed computing theory › fault tolerance › byzantine fault tolerance
byzantine agreement
0.021987
An O(log n) expected rounds randomized byzantine generals protocol · J. ACM 1987
Asynchronous Consensus and Broadcast Protocols · J. ACM 1985
Distributed systems
consensus
0.021987
Asynchronous Byzantine Agreement Protocols · Inf. Comput. 1987
Resilient Consensus Protocols · PODC 1983
Distributed systems › consensus
byzantine agreement
0.011987
Asynchronous Byzantine Agreement Protocols · Inf. Comput. 1987
Distributed computing theory › randomization
randomized protocols
0.011987
An O(log n) expected rounds randomized byzantine generals protocol · J. ACM 1987
Distributed systems › consensus
byzantine broadcast
0.011985
An O(\mathop lg n) Expected Rounds Randomized Byzantine Generals Protocol · STOC 1985
Distributed systems › consensus › byzantine broadcast
randomized byzantine agreement
0.011985
An O(\mathop lg n) Expected Rounds Randomized Byzantine Generals Protocol · STOC 1985
Distributed computing theory › fault tolerance › byzantine fault tolerance › byzantine agreement
asynchronous byzantine agreement
0.011985
Asynchronous Consensus and Broadcast Protocols · J. ACM 1985
Distributed computing theory › consensus
consensus protocols
0.011985
Asynchronous Consensus and Broadcast Protocols · J. ACM 1985
Distributed systems › consensus › fault-tolerant consensus
asynchronous consensus
0.011984
An Asynchronou [(n-1)/3]-Resilient Consensus Protocol · PODC 1984
Distributed systems › concurrency control
deadlock detection
0.011984
A Distributed Algorithm for Generalized Deadlock Detection · PODC 1984
Distributed systems
distributed algorithms
0.011984
A Distributed Algorithm for Generalized Deadlock Detection · PODC 1984
Cloud and datacenter computing
resource allocation
0.011984
A Distributed Algorithm for Generalized Deadlock Detection · PODC 1984
Distributed computing theory › consensus
t-resilient consensus
0.011984
An Asynchronou [(n-1)/3]-Resilient Consensus Protocol · PODC 1984
Distributed systems › fault tolerance › fault-tolerant distributed systems
fail-stop fault tolerance
0.011983
Resilient Consensus Protocols · PODC 1983
Distributed systems › fault tolerance
resilience
0.011983
Resilient Consensus Protocols · PODC 1983

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

randomization · 0.0randomized protocol · 0.0probabilistic protocol · 0.0cryptographic methods · 0.0
YearPublicationVenuePosition
1987 Distributed Deadlock Detection
Gabriel Bracha, Sam Toueg
Distributed Comput.1
1987 Asynchronous Byzantine Agreement Protocols
Gabriel Bracha
Inf. Comput.1
1987 An O(log n) expected rounds randomized byzantine generals protocol
abstract
Byzantine Generals protocols enable processes to broadcast messages reliably in the presence of faulty processes. These protocols are run in a system that consists of n processes, t of which are faulty. The protocols are conducted in synchronous rounds of message exchange. It is shown that, in the absence of eavesdropping, without using cryptography, for any ε > 0 and t = n /(3 + ε), there is a randomized protocol with O (log n ) expected number of rounds. If cryptographic methods are allowed, then, for ε > 0 and t = n /(2 + ε), there is a randomized protocol with O (log n ) expected number of rounds. This is an improvement on the lower bound of t + 1 rounds required for deterministic protocols, and on a previous result of t /log n expected number of rounds for randomized noncryptographic protocols.
Gabriel Bracha
J. ACM1
1985 An O(\mathop lg n) Expected Rounds Randomized Byzantine Generals Protocol
abstract
Byzantine Generals protocols enable processes to reliably broadcast messages in the presence of faulty processes. These protocols are run in a system of consists of n processes, t of which are faulty. The protocols are conducted in synchronous rounds of message exchange. We show that, without using cryptography, for t = n/(3 + d), there is a randomized protocol with O(lg n) expected number of rounds. If we allow cryptographic methods, then, for t = n / (2 + d), there is a randomized protocol with O(lg n) expected number of rounds. This is an improvement on the lower bound of t + 1 rounds required for det … … previous result of t/lg n expected nu rounds for randomized protocols.
Gabriel Bracha
STOC1
1985 Asynchronous Consensus and Broadcast Protocols
abstract
A consensus protocol enables a system of n asynchronous processes, some of which are faulty, to reach agreement. There are two kinds of faulty processes: fail-stop processes that can only die and malicious processes that can also send false messages. The class of asynchronous systems with fair schedulers is defined, and consensus protocols that terminate with probability 1 for these systems are investigated. With fail-stop processes, it is shown that ⌈( n + 1)/2⌉ correct processes are necessary and sufficient to reach agreement. In the malicious case, it is shown that ⌈(2 n + 1)/3⌉ correct processes are necessary and sufficient to reach agreement. This is contrasted with an earlier result, stating that there is no consensus protocol for the fail-stop case that always terminates within a bounded number of steps, even if only one process can fail. The possibility of reliable broadcast (Byzantine Agreement) in asynchronous systems is also investigated. Asynchronous Byzantine Agreement is defined, and it is shown that ⌈(2 n + 1)/3⌉ correct processes are necessary and sufficient to achieve it.
Gabriel Bracha, Sam Toueg
J. ACM1
1984 An Asynchronou [(n-1)/3]-Resilient Consensus Protocol
abstract
A consensus protocol enables a system of n asynchronous processes, some of them malicious, to reach agreement. No assumptions are made on the behaviour of the processes and the message system; both are capable of colluding to prevent the correct processes from reaching decision. A protocol is t-resilient if in the presence of up to t malicious processes it reaches agreement with probability 1. In a recent paper, t-resilient consensus protocols were presented for t<n/5. We improve this to t
Gabriel Bracha
PODC1
1984 A Distributed Algorithm for Generalized Deadlock Detection
abstract
An efficient distributed algorithm to detect deadlocks in distributed and dynamically changing systems is presented. In our model, processes can request any $N$ available resources from a pool of size $M$. This is a generalization of the well-known AND-OR request model. The algorithm is incrementally derived and proven correct. Its communication, computational, and space complexity compares favorably to those of previously known distributed AND-OR deadlock detection algorithms.
Gabriel Bracha, Sam Toueg
PODC1
1983 Resilient Consensus Protocols
abstract
A consensus protocol enables a system of n asynchronous processes, some of which are faulty, to reach agreement. There are two kinds of faulty processes: fail-stop processes can only die, malicious processes can also send false messages. We investigate consensus protocols that terminate within finite time with probability 1 under certain assumptions on the behavior of the system. With fail-stop processes, we show that [(n + 1)/2] correct processes are necessary and sufficient to reach agreement. In the malicious case, we show that [(2n + 1)/3] correct processes are necessary and sufficient to reach agreement. This is contrasted with a recent result that there is no consensus protocol for the fail-stop case that always terminates within a bounded number of steps, even if only one process can fail.
Gabriel Bracha, Sam Toueg
PODC1