A Case Study in Rewriting a Critical Service in Rust
Posted4 months agoActive4 months ago
wxiaoyun.comTechstory
calmpositive
Debate
20/100
RustPerformance OptimizationSystem ProgrammingLanguage Comparison
Key topics
Rust
Performance Optimization
System Programming
Language Comparison
A company rewrote a critical service in Rust, achieving significant cost savings and performance improvements, sparking discussion on the trade-offs and alternatives to rewriting in a new language.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
9m
Peak period
1
0-1h
Avg / period
1
Key moments
- 01Story posted
Sep 1, 2025 at 12:22 AM EDT
4 months ago
Step 01 - 02First comment
Sep 1, 2025 at 12:30 AM EDT
9m after posting
Step 02 - 03Peak activity
1 comments in 0-1h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 1, 2025 at 1:55 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45089424Type: storyLast synced: 11/20/2025, 10:59:01 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.
Dam those are some expensive vCPUs. $750 per vCPU per year. It probably accounts the memory savings too but still.
It would be nice to read about what they did try before rewritting. They mention flamegraphs but nothing specific.
In my Go experience while working with fintech, Go API services can become CPU bound with excessive context switching if GOMAXPROCS is not well tunned in hot services and also with things like string maps. These tend to be easy to catch with pprof. I've had some 2x speedups with those. Certainly they already checked those quick wins I presume.