We Deleted Tokio From Our Payment System and Cut Cloud Costs by $127,000
Posted2 months agoActive2 months ago
medium.comTechstory
calmpositive
Debate
20/100
Async ProgrammingCloud CostsTokio
Key topics
Async Programming
Cloud Costs
Tokio
A company removed Tokio from their payment system, resulting in significant cloud cost savings, and sparking discussion on the trade-offs of using async frameworks.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
30s
Peak period
5
0-1h
Avg / period
5
Key moments
- 01Story posted
Oct 31, 2025 at 2:36 PM EDT
2 months ago
Step 01 - 02First comment
Oct 31, 2025 at 2:37 PM EDT
30s after posting
Step 02 - 03Peak activity
5 comments in 0-1h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 31, 2025 at 3:26 PM EDT
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45775213Type: storyLast synced: 11/17/2025, 8:11:09 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Most of us have been bitten by this naive mistake and I'm sure we have learned our lesson.
This only happens if you're using blocking code in the event loop, right? This article seems like an admission of over-engineering from the get go.