Production-ready Go

on YouTube ↗35m

" summary

Go's net/http defaults are dangerous: the package-level HTTP client lacks a timeout (though Transport sometimes times out) and ListenAndServe omits server timeouts, so untrusted slow clients can exhaust file descriptors; a local demo shows 1.2M requests in 60s at 20k/s and 195µs avg but a ulimit=20 test with a 10bps slow client fills descriptors. Fixes are minimal: set ReadTimeout/WriteTimeout/IdleTimeout on http.Server, handle SIGINT and SIGTERM via signal.Notify, and propagate cancellation with request.Context().Done().

AI-written summary · about

" chapters (16)

1. 0:00Intro
2. 2:15Seriously bad code
3. 2:28Productionready Go
4. 2:58Things I wont be talking about
5. 3:20Easy
6. 4:40Mistakes
7. 5:58Client timeouts
8. 6:27HTTP timeouts
9. 10:22HTTP server demo
10. 15:18HTTP server tips
11. 18:18Operating system signals
12. 19:21OS signals overview
13. 21:43Sigmapipe overview
14. 26:40Cancellation overview
15. 27:48Cancellation in Go
16. 32:37Recap

" related talks

• 47mUsing Go in DevOpsNatalie Pistunovich · DevOps Conference 2018
• 06mHow Not to DDOS ServersJessica Xie · GopherCon 2019
• 37mBest Practices for Cloud-Native Go ServicesElena Grahovac · GoWayFest 2.0 2018
• 29mBest Practices for Production EnvironmentsPeter Bourgon · GopherCon 2014
• 33mThe Gotchas of Zero-Downtime Traffic /w KubernetesLeigh Capili · KubeCon + CloudNativeCon North America 2019
• 01h 00mOptimizing your HttpClient usageNico Vermeir · NDC London 2026
• 43mUsage of Go in VK's Infrastructure TasksAleksey Akulovich · GoWayFest 2.0 2018
• 21mMaking Docker GO: Why One of the Fastest Growing Open Source ProjectsVictor Vieux · GopherCon 2014