node.js in production use
summary
A working temporary-email proxy called temp alias generates non-guessable random addresses, stores them in Redis, and serves the front end with Paperboy while using a patched node-smtp and nginx plus iptables to appear on port 25. The system hits ~50–500 alias generations/sec and ~3,000 lookups/sec, handles Hacker News bursts, and has produced ~200,000 aliases. Production issues: socket leaks requiring weekly restarts, spam abuse fixed with RBL checks and rate limits, and planned custom domains and reply-address rewriting.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:34Temp alias service
- 3:41User interface design
- 6:36Design flaws and changes
- 7:59Redis for alias storage
- 9:45Alias expiration cleanup
- 10:29Dependencies and fixes
- 11:52Static HTML and API
- 12:54Paperboy for static files
- 13:36Node.js benchmarks
- 14:40Bookmarklet challenges
- 15:45Traffic spikes and spam
- 17:31Production setup security
- 18:37Node.js exception pitfalls
- 20:02Future improvements
related talks
42mThe Node.js Highway: Attacks Are At Full Throttle
31mNode.js that's hugely reliable, fast, and scalable
40mDeploying node.js at scale
22mNode.js at UBER
53mMastering Node.js Performance
19mRunning Node.js in Production
24mArchitect for Scale - My Learnings in Node.js (A case study)
18mNode at Mail Online