Resend – Migrating our email API to go
Comments on “Resend – Migrating our email API to go”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Resend rewrote its email API from Node to Go in seven weeks and about 140 pull requests, and says Go now handles all traffic. At a 50% split, it reports median POST /emails latency of 31 ms versus 58 ms, p99 of 420 ms versus 498 ms, and about 62% less CPU per request. Peak tasks fell from 34 to 10. A harness compared responses, database rows, S3 objects and rate limits. The figures are Resend's own, unverified, and task sizes still had to be doubled twice.
Why it ranked
No. 12 of 123 with a score of 0.66. The panel rated it highest on new information (0.91) and substantiated (0.85), lowest on audience breadth (0.52). Placed No. 12, No. 20 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- A detailed engineering write-up of migrating a production email API from Node to Go, with benchmarks, parity testing and rollout lessons; well-substantiated and practical, though niche in audience.
- AI judgeJudge 3gpt-5.6-luna
- A well-supported engineering write-up with concrete compatibility testing, migration tactics, rollout lessons, and production metrics. It is highly actionable for teams rewriting critical APIs, though its significance is mainly within backend and infrastructure engineering.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.66total under rubric v2.3
- Significance0.52
- Reader interest0.80
- Audience breadth0.52
- Practical relevance0.78
- Substantiated0.85
- Technical depth0.78
- New information0.91
- Counts against: Promotional0.10
- Counts against: Overclaim0.17
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.50 | 0.45 | 0.62 | 0.52 | 0.17 | +0.24 | +0.126 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.71 | 0.80 | 0.88 | 0.80 | 0.17 | +0.26 | +0.207 |
| Audience breadthHow many people who build technology does it concern? | 0.47 | 0.50 | 0.58 | 0.52 | 0.11 | +0.13 | +0.067 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.81 | 0.70 | 0.82 | 0.78 | 0.12 | +0.22 | +0.171 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.94 | 0.70 | 0.91 | 0.85 | 0.24 | +0.05 | +0.042 |
| Technical depthHow technically substantive is it? | 0.86 | 0.70 | 0.78 | 0.78 | 0.16 | +0.05 | +0.039 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.90 | 0.96 | 0.91 | 0.08 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.05 | 0.20 | 0.06 | 0.10 | 0.15 | −0.19 | −0.020 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.17 | 0.25 | 0.08 | 0.17 | 0.17 | −0.11 | −0.018 |
| Sum of contributions | +0.660 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.659 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-14/12/"><img src="https://rubric.hrih.si/badge/2026-11-14/12.svg" alt="Ranked #12 on Rubric, 14 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
Resend built a new Go service from an empty project to production traffic in seven weeks and roughly 140 pull requests.
The article gives no link or citation for it.
The article says “Over seven weeks and roughly 140 pull requests, we took a new Go service from an empty project to production traffic”
The source says No source to compare with.
No source givenNumber
While traffic was split evenly between the Node and Go services, Go showed roughly half the median latency and about one-seventh the memory usage per task.
The article gives no link or citation for it.
The article says “Go showed roughly half the median latency and about one-seventh the memory usage per task”
The source says No source to compare with.
No source givenDate
By October, Go was handling all of Resend's email API traffic.
The article gives no link or citation for it.
The article says “By October, Go was handling all our email API traffic”
The source says No source to compare with.
No source givenNumber
At the 50% rollout, with both services on the same task size, the Go service used about 62% less CPU per request.
The article gives no link or citation for it.
The article says “Both services ran on the same task size and the Go service used about 62% less CPU per request”
The source says No source to compare with.
No source givenNumber
Median latency for POST /emails fell by roughly 50% and p99 fell by about 16% with Go.
The article gives no link or citation for it.
The article says “Median latency for POST requests to /emails fell by roughly 50%, while p99 fell by about 16%”
The source says No source to compare with.
No source givenNumber
The initial Go port of the HTML-to-text behavior matched all 60 fixtures generated from the Node implementation exactly.
The article gives no link or citation for it.
The article says “The initial port matched all 60 fixtures generated from the Node implementation exactly”
The source says No source to compare with.
No source givenNumber
Tasks at peak dropped from 34 on Node to 10 on Go, and memory per task from about 1.3 GB to about 180 MB.
The article gives no link or citation for it.
The article says “Tasks at peak 34 10”
The source says No source to compare with.
No source givenCausal conclusion
Parsing and serializing large request bodies, including ones already rejected by the rate limiter, made whole Node tasks unresponsive during bursts by blocking the event loop.
The article gives no link or citation for it.
The article says “One investigation traced this to parsing and serializing large request bodies, including requests that were already being rejected by the rate limiter”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 6 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:44 UTC. It played no part in the ranking.