Nov 22, 2026 · 18 min · 9 segments
Learn more about your ad choices. Visit megaphone.fm/adchoices
When you're first building an application, transactions are easy.
You have a database, and when a customer places an order, you wrap the whole thing in the transaction.
Charge their card, reserve the inventory, record a ledger entry for accounting.
If any of those rights fails, the database rolls everything back automatically, and it's just like nothing happened.
You probably don't even think about it much.
Your database gives you what are called asset guarantees, which basically means two things that matter here.
First, atomicity.
Either all three of those rights happen together, or none of them do.
There's no world where the card gets charged, but the inventory doesn't get reserved.
Second is isolation.
While that transaction is in progress, no other part of your system can see the half-finished state.
Another query checking the customer's balance won't see a charge for an order that hasn't fully processed yet.
The database handles all of this behind the scenes, and you just write your SQL and move on.
But when your application grows, you start to get more traffic, more data, more writes, and eventually that single database starts hitting its limits.
So you do what everyone does at this point.
You split things up.
Maybe you shard the database to spread write load across multiple machines, or maybe you break up your monolith into microservices, where each service now owns its own database.
The specifics can vary, but the result is the same.
Your data now lives on multiple independent machines instead of one.
And at this point, everything changes.
The payment flow that used to be one transaction against one database is now three completely separate operations against three separate databases on three separate machines.
The card gets charged to the payment database, inventory gets reserved in the inventory database, and that ledger entry gets recorded in the accounting database.
You can't wrap a transaction across these independent databases because they don't know about each other.
So if the card charge commits, but then the inventory reservation fails because the item is out of stock, there's no database level rollback that can undo that charge.
It's already committed in a completely different database on a completely different machine.
When you're first building an application, transactions are easy.
You have a database, and when a customer places an order, you wrap the whole thing in the transaction.
Charge their card, reserve the inventory, record a ledger entry for accounting.
If any of those rights fails, the database rolls everything back automatically, and it's just like nothing happened.
You probably don't even think about it much.
Your database gives you what are called asset guarantees, which basically means two things that matter here.
First, atomicity.
Either all three of those rights happen together, or none of them do.
There's no world where the card gets charged, but the inventory doesn't get reserved.
Second is isolation.
While that transaction is in progress, no other part of your system can see the half-finished state.
Another query checking the customer's balance won't see a charge for an order that hasn't fully processed yet.
The database handles all of this behind the scenes, and you just write your SQL and move on.
But when your application grows, you start to get more traffic, more data, more writes, and eventually that single database starts hitting its limits.
So you do what everyone does at this point.
You split things up.
Maybe you shard the database to spread write load across multiple machines, or maybe you break up your monolith into microservices, where each service now owns its own database.
The specifics can vary, but the result is the same.
Your data now lives on multiple independent machines instead of one.
And at this point, everything changes.
The payment flow that used to be one transaction against one database is now three completely separate operations against three separate databases on three separate machines.
The card gets charged to the payment database, inventory gets reserved in the inventory database, and that ledger entry gets recorded in the accounting database.
You can't wrap a transaction across these independent databases because they don't know about each other.
So if the card charge commits, but then the inventory reservation fails because the item is out of stock, there's no database level rollback that can undo that charge.
It's already committed in a completely different database on a completely different machine.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.