5. Going To Production Practices

• 5.1. Monitoring
• 5.2. Increase transparency using smart logging
• 5.3. Delegate anything possible (e.g. gzip, SSL) to a reverse proxy
• 5.4. Lock dependencies
• 5.5. Guard process uptime using the right tool
• 5.6. Utilize all CPU cores
• 5.7. Create a ‘maintenance endpoint’
• 5.8. Discover errors and downtime using APM products
• 5.9. Make your code production-ready
• 5.10. Measure and guard the memory usage
• 5.11. Get your frontend assets out of Node
• 5.12. Be stateless, kill your servers almost every day
• 5.13. Use tools that automatically detect vulnerabilities
• 5.14. Assign a transaction id to each log statement
• 5.15. Set NODE_ENV=production
• 5.17. Use an LTS release of Node.js
• 5.18. Don‘t route logs within the app
• 5.19. Install your packages with npm ci