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

Cuong D. T. Nguyen

dblp:350/5694 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
2since 2021 · last 2025
0000-0003-4250-2896ORCID · corroborated

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

Databases, data management, data science and information retrieval · 2 · 2 first-author · 2 since 2021

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
2 papers
Transaction processing and concurrency control · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%
Software engineering, system software, and programming languages
1 paper
Empirical software engineering · 100%

Topics — the 5 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Transaction processing and concurrency control
concurrency control
1.522025
Are Database System Researchers Making Correct Assumptions about Transaction Workloads? · Proc. ACM Manag. Data 2025
Detock: High Performance Multi-region Transactions at Scale · Proc. ACM Manag. Data 2023
Transaction processing and concurrency control › deadlock
deadlock resolution
0.712023
Detock: High Performance Multi-region Transactions at Scale · Proc. ACM Manag. Data 2023
Distributed systems › replication
geo-replication
0.712023
Detock: High Performance Multi-region Transactions at Scale · Proc. ACM Manag. Data 2023
Distributed systems › distributed database
multi-site transactions
0.712023
Detock: High Performance Multi-region Transactions at Scale · Proc. ACM Manag. Data 2023
Empirical software engineering
mining software repositories
0.312025
Are Database System Researchers Making Correct Assumptions about Transaction Workloads? · Proc. ACM Manag. Data 2025

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

transaction workload analysis · 1.7empirical study · 1.7pessimistic concurrency control · 1.3optimistic concurrency control · 1.3
YearPublicationVenuePosition
2025 Are Database System Researchers Making Correct Assumptions about Transaction Workloads?
abstract
Many recent papers have contributed novel concurrency control and transaction processing algorithms that start by making an assumption about the transaction workload submitted by an application, and yield high performance (sometimes by an order of magnitude) under these assumptions. Two of the most common assumptions are (1) Is the read and write set of a transaction known (or easily derivable) directly by analyzing the application code in advance of transaction execution, or is the access set of a transaction dependent on the current state of the database? (2) Does the application send the entire transaction in a single request to the database system or is the transaction sent via several requests ''interactively'', with application code run in between these requests. The database community has made tremendous progress in improving throughput and latency of transaction processing when read/write sets are known in advance, and for non-interactive transactions. However, the impact of this progress is directly dependent on the accuracy of these assumptions both for current and future applications. In this paper, we conduct an extensive study of 111 open-source applications, analyzing over 30,000 transactions to evaluate the accuracy of these assumptions both as they exist in the current codebase, and how extensive are the changes required to the code for these assumptions to hold moving forward. Our study reveals that the second of these assumptions is stronger than the first. More specifically, for 90% of applications, at least 58% of transactions per application have read/write sets that can be inferred in advance. Furthermore, although only 39% of applications contain zero interactive transactions, nonetheless, the majority of the remaining 61% of applications can be converted to being completely non-interactive with minimal changes.These insights underscore the potential for further optimization and research in designing OLTP systems that balance transaction expressivity and performance.
Cuong D. T. Nguyen, Christopher DeCarolis, Daniel J. Abadi
Proc. ACM Manag. Data1
2023 Detock: High Performance Multi-region Transactions at Scale
abstract
Many globally distributed data stores need to replicate data across large geographic distances. Since synchronously replicating data across such distances is slow, those systems with high consistency requirements often geo-partition data and direct all linearizable requests to the primary region of the accessed data. This significantly improves performance for workloads where most transactions access data close to where they originate from. However, supporting serializable multi-geo-partition transactions is a challenge, and they often degrade the performance of the whole system. This becomes even more challenging when they conflict with single-partition requests, where optimistic protocols lead to high numbers of aborts, and pessimistic protocols lead to high numbers of distributed deadlocks. In this paper, we describe the design of concurrency control and deadlock resolution protocols, built within a practical, complete implementation of a geographically replicated database system called Detock, that enables processing strictly-serializable multi-region transactions with near-zero performance degradation at extremely high conflict and order of magnitude higher throughput relative to state-of-the art geo-replication approaches, while improving latency by up to a factor of 5.
Cuong D. T. Nguyen, Johann K. Miller, Daniel J. Abadi
Proc. ACM Manag. Data1