P. C. Aristides

dblp:50/1636 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1992
—ORCID · none

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

Databases, data management, data science and information retrieval · 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.

Databases, data mining, and information retrieval
1 paper
Transaction processing and concurrency control · 75% Distributed and cloud data management · 25%
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

TopicWeightPapersLastEvidence papers
Distributed and cloud data management
data replication
0.011992
Fast Read-Only Transactions in Replicated Databases · ICDE 1992
Transaction processing and concurrency control
distributed commit protocols
0.011992
Fast Read-Only Transactions in Replicated Databases · ICDE 1992
Transaction processing and concurrency control › transaction models
read-only transaction
0.011992
Fast Read-Only Transactions in Replicated Databases · ICDE 1992
Transaction processing and concurrency control › distributed commit protocols
two-phase commit
0.011992
Fast Read-Only Transactions in Replicated Databases · ICDE 1992
Distributed systems
fault tolerance
0.011992
Fast Read-Only Transactions in Replicated Databases · ICDE 1992
Distributed systems
replication
0.011992
Fast Read-Only Transactions in Replicated Databases · ICDE 1992

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

quorum protocol · 0.0commit propagation · 0.0
YearPublicationVenuePosition
1992 Fast Read-Only Transactions in Replicated Databases
abstract
The authors present a propagation mechanism, called the commit propagation mechanism (CPM), which increases the availability of data for read-only transactions. The proposed mechanism is piggy-backed on the messages used in the two-phase commit protocol. The CPM was combined with the standard quorum protocol in two different replicated database systems. In a fully replicated database, CPM allows any read-only transaction to execute locally at a single site without the need for any communication overhead. In a partially replicated database, CPM either ensures that the set of copies residing at a site are mutually consistent, or indicates which copies violate such consistency.>
P. C. Aristides, Amr El Abbadi
ICDE1