Study
Innovation & MarketsHigh ImpactStrong effect

Bridging Transactional Gaps: Enabling ACID Compliance Across Heterogeneous NoSQL Data Stores

A novel client-coordinated protocol and API extension (REST+T) allows applications to achieve ACID transactional guarantees across diverse NoSQL data stores, even those lacking native multi-item transaction support.

The Sydney eScholarship Repository (The University of Sydney) · 2015

01

Key Findings

  • 01A client-coordinated protocol can enable ACID transactions across heterogeneous NoSQL data stores.
  • 02The REST+T API provides a standardized way to express transactional operations.
  • 03YCSB+T benchmark effectively measures transactional throughput and detects data store anomalies.
02

Application

Design takeaway

When designing systems that utilize multiple NoSQL data stores, consider implementing a client-side transaction management layer to ensure data integrity for critical operations.

How to apply

When integrating different database services for a single application, develop a middleware or client library that orchestrates operations across these services to enforce transactional consistency.

Project actions

  • 01When choosing data stores for a project, consider if any part of your application needs strong consistency.
  • 02Explore how to build a simple transaction manager for a small set of data operations.
03

Method & Evidence

AimHow can ACID transactional guarantees be achieved across heterogeneous NoSQL data stores that individually only support single-item transactions?
MethodProtocol Design and Prototyping
ProcedureThe researchers defined a client-coordinated transaction commitment protocol (Cherry Garcia) built upon an extended HTTP API (REST+T). They developed prototype implementations for Windows Azure Storage, Google Cloud Storage, and a new system called Tora. The YCSB benchmark was extended to YCSB+T to evaluate the system's performance and ability to detect anomalies.
ContextCloud computing, distributed systems, database management, software development

Variables

IV["Type of NoSQL data store","Transaction coordination protocol"]
DV["Transactional success rate (ACID compliance)","Throughput (operations per second)","Anomaly detection rate"]
CV["Network latency","Data store load","Complexity of transaction"]
04

Strengths & Limitations

Strengths

  • +Addresses a significant practical problem in modern distributed systems.
  • +Provides a concrete protocol and benchmark for evaluation.

Limitations

The proposed solution adds complexity and potential latency compared to native transactional systems.

Reliability & validity

The use of a benchmark like YCSB+T and prototype implementations lends validity. Reliability would depend on the stability of the underlying data stores and network conditions during testing.

Think critically

What are the potential failure points in a client-coordinated transaction protocol, and how might these be mitigated?

05

Design Principles

"Decouple transactional logic from individual data stores by implementing a client-coordinated protocol."

Many modern applications leverage the scalability of NoSQL databases but face challenges when specific functionalities require strict transactional integrity. This research provides a practical solution for developers to integrate transactional capabilities without abandoning existing NoSQL infrastructure, opening up new market opportunities for applications previously constrained by data consistency limitations.

06

What This Means for Your Design

You can make different types of databases work together to handle complex transactions, even if they don't normally support them, by using a clever system on the computer that talks to them.

How to use in your project

  • 1.Reference this study when discussing the challenges of data consistency in distributed systems or when proposing solutions for transactional integrity in your design project.
07

Add to My Project

08

Quick Cite

(2015). Cherry Garcia: Transactions across Heterogeneous Data Stores. The Sydney eScholarship Repository (The University of Sydney). Retrieved from https://designdex.org/study/a98d81d4-3712-4763-a314-94f9f7797928/bridging-transactional-gaps-enabling-acid-compliance-across-heterogeneous-nosql-data-stores

Paragraph starter

The challenge of achieving ACID transactional guarantees across heterogeneous NoSQL data stores, which often lack native multi-item transaction support, can be addressed through client-coordinated protocols. As demonstrated by Cherry Garcia, a system built on REST+T, it is possible to enable robust transactional capabilities by managing operations at the client level, thereby expanding the application domains for scalable data storage solutions.

09

Source

The Sydney eScholarship Repository (The University of Sydney)

Cherry Garcia: Transactions across Heterogeneous Data Stores

journal · 2015

View source

Questions about this research

What does the research say about bridging transactional gaps: enabling acid compliance across heterogeneous nosql data stores?
When designing systems that utilize multiple NoSQL data stores, consider implementing a client-side transaction management layer to ensure data integrity for critical operations. Evidence: The Sydney eScholarship Repository (The University of Sydney) (2015).
Why does "Bridging Transactional Gaps: Enabling ACID Compliance Across Heterogeneous NoSQL Data Stores" matter for design?
Many modern applications leverage the scalability of NoSQL databases but face challenges when specific functionalities require strict transactional integrity. This research provides a practical solution for developers to integrate transactional capabilities without abandoning existing NoSQL infrastructure, opening up new market opportunities for applications previously constrained by data consistency limitations.
How can designers apply this research?
When designing systems that utilize multiple NoSQL data stores, consider implementing a client-side transaction management layer to ensure data integrity for critical operations.
What were the main findings?
A client-coordinated protocol can enable ACID transactions across heterogeneous NoSQL data stores.. The REST+T API provides a standardized way to express transactional operations.. YCSB+T benchmark effectively measures transactional throughput and detects data store anomalies.
What research method was used?
Protocol Design and Prototyping.
How strong is the evidence?
Evidence strength is rated Strong effect, based on a 2015 journal from The Sydney eScholarship Repository (The University of Sydney).
What should I do differently in my next project?
When integrating different database services for a single application, develop a middleware or client library that orchestrates operations across these services to enforce transactional consistency.
What are the limitations?
Performance overhead associated with client-side coordination; reliance on individual data stores supporting at least single-item transactions; complexity of managing distributed transactions.
Is there evidence that data stores affects design outcomes?
It's possible to implement ACID transactions across different NoSQL databases by using a smart client-side coordination system, even if the databases themselves don't natively support complex transactions. Many modern applications leverage the scalability of NoSQL databases but face challenges when specific functionali Source: The Sydney eScholarship Repository (The University of Sydney) (2015).
Where does this nosql research apply?
Cloud computing, distributed systems, database management, software development It sits within innovation & markets research on designdex.org.

Related research topics

data stores design research · evidence on data stores · does data stores improve design outcomes · nosql studies for designers · data stores and nosql findings · innovation & markets research evidence