-
Notifications
You must be signed in to change notification settings - Fork 30
message broker blog post #990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| @@ -0,0 +1,127 @@ | |||
| --- | |||
| title: From Barter to Brokers, Why Synchronous Thinking Breaks at Scale | |||
| description: Explore how asynchronous thinking transforms software architecture, just like money revolutionized economies by decoupling exchanges in time. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"just like how money", delete "in time"
|
|
||
| In a **barter economy**, that's a significant challenge. The grocer won't trade until her inventory system is fixed. The database admin won't help until his kid gets dental care. The dentist won't see patients until her taxes are filed. The accountant won't do taxes until his computer is repaired. And the computer repair shop? They need custom diagnostic software built. | ||
|
|
||
| Your dinner depends on five people showing up in sequence, perfectly aligned. If the dentist's booked solid, you don't eat. If the accountant's in audit season, the chain collapses. Barter is **synchronous and tightly coupled**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"if the dentist is booked solid"
"bartering is synchronous and tightly coupled"
|
|
||
| You write software today, get paid, and buy groceries tomorrow. The farmer sells produce on Tuesday, pays the roofer on Friday, and the lawyer gets her fee next month. Each exchange stands alone. Failures don't cascade. The medium of exchange **decouples everyone in time**. | ||
|
|
||
| But there's a crucial distinction in how this asynchronous magic happens. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
occurs instead of "happens"
|
|
||
| When money changes hands as **cash**, it's like a **queue**: you hand over value, and it sits with the other person until they spend it. The system works asynchronously, but the "message" is literally in transit from one hand to another. | ||
|
|
||
| With **banking**, something more powerful emerges. The **bank** doesn't move money physically—it holds accounts, routes payments, and makes sure funds arrive reliably and durably even when people aren't present. That's exactly what a **message broker** does in software. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
delete "and durably"
|
|
||
| With **banking**, something more powerful emerges. The **bank** doesn't move money physically—it holds accounts, routes payments, and makes sure funds arrive reliably and durably even when people aren't present. That's exactly what a **message broker** does in software. | ||
|
|
||
| **The key point**: Asynchronous operation requires trusted intermediaries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
operations?
No description provided.