Distributed Transaction

Case Study @

101

Why Change the Topic?

Billing/Payment Systems

Scope

• Microservices
• Distributed Storages
• Machine Learning

Prerequisite

• What is transactions in RDBMS
• What is consensus algorithms

Content

• What is dist transactions?
• Challenges in distributed transactions
• Solutions 0 - 4
• Cases Study

Transaction

A transaction is a single unit of logic or work, sometimes made up of multiple operations -

​

• To provide reliable units of work.
• To provide isolation between programs accessing a database concurrently.

Transaction

A transaction is a single unit of logic or work, sometimes made up of multiple operations -

​

• To provide reliable units of work.
• To provide isolation between programs accessing a database concurrently.

Transaction

A database transaction, by definition, must be -

​

ACID

ACID

• Atomicity - Transaction steps are indivisible
• Consistency - A transaction should only bring the database from one valid state to another valid state
• Isolation - Multiple concurrently transactions should be able to run without interference
• Durability - Persisted and survive failures

Isolation Levels - Serializability

Dist Transaction

How about the timing?

Serializability is a property of multiple operations executed in arbitrary order.

​

How about the timing?

Timing is not important

Timing is important!

Timing is important!

Solutions 0

2 Phase Commit -

​

Solutions - 1

Base -

• Basically Available
• Soft State
• Eventually Consistent

Solutions - TCC

TCC

​

Solutions - SAGA

SAGA

​

Solutions - 2

Dist SQL

Solutions - Spanner

Spanner

​

Dist SQL

• TiDB - TiDB Cloud
• Cockroach - Cockroach Serverless
• Yugabyte
• NoSQL etc.

​

Solutions - 3

Deterministic Database

Solutions

Calvin

​

Solutions - 4?

Machine Learning

Solutions

Polyjuice

​

Case Study

Thank You!