Top 21 Node.js production best practices
Even the most accomplished IT/DevOps guy can’t save a system that is poorly written. So code with the end in mind, plan for production from day one. Meaning, ensuring you save no data locally on a specific web server, utilizing cache heavily, gauging memory usage and leaks, minimizing the usage of anonymous functions, making use of CI tools to detect failures before sending to production, logging wisely and having an error handling strategy in place from the very start. Below are a set of practices we’ve developed along the way that have served us well.
Read more