From Node.js to Go
summary
A team switches a majority Node.js codebase to Go using a pragmatic framework: piecemeal migration, separated processes and RPC proxies that keep front ends and stream ingestion decoupled. Porting core text processing to Go yields 64% faster throughput; UTF‑8 handling and Go concurrency primitives reduce latency under heavy multilingual loads. The result is a running service that becomes a 90% Go backend, survives a DDoS spike, and lets teams iterate without stopping feature work.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:30Why Nodejs
- 4:17PopTip
- 5:02Technical Debt
- 6:33Drop the Boss
- 6:51Switch Languages
- 7:27Breaking Point
- 8:22Immediate Value
- 11:49Time
- 12:27Moving Forward
- 13:33piecemeal approach
- 14:58what was great
- 15:48what happened
- 16:10how we handled it alone
- 17:47why not 100 go
related talks
05mMaking the Leap from NodeJS to Go
22mHappy Path to Go – Transitioning teams to Golang
33mGOLANG USAGE IN DEVELOPMENT OF NODE.JS APPLICATIONS (NODE.JS: IN GO WE TRUST)
49mGet GOing with a New Language
49mFrom Java to Golang, the journey of the nexuzhealth team
31mHow Go is Making us Faster
39mPorting the TypeScript Compiler to Go for a 10x Speedup V2
58mGet GOing with a New Language