• How to Optimize Enterprise-Scale Node.js Applications
  • Original post by AppDynamics
  • The Nuggets translation Project
  • Permanent link to this article: github.com/xitu/gold-m…
  • Translator: Starrier
  • Proofreader: GeniusQ1981

conclusion

Cisco (AppDynamics) ranked no. 1 in this year’s APM report. Download Gartner’s 2018 Magic Quadrant to learn more about APM!

Get advanced Node.js success guides to discover expert techniques for optimizing, deploying, and maintaining enterprise-class Node.js applications.

Node.js is fast becoming one of the most popular platforms for building fast, scalable Web and mobile applications. In fact, according to the 2017 Node.js User survey, there are currently over 7 million Node.js instances online, and three-quarters of users plan to increase their Node.js usage in the next 12 months. It’s easy to see why: 68% of users think Node.js increases developer productivity, 58% think Node.js reduces development costs, and 50% think Node.js improves application performance.

Node.js is becoming the technology of choice for application development, and the demand for Professional Node.js developers is also increasing. While there has been a lot written about what Node.js can do, how developers are starting to use it, and why it’s becoming a core server technology for some of the world’s largest companies — not much has actually been done to help beginner or intermediate Node.js developers improve their current technology. So far.

In our latest eBook, Advanced Node.js: Optimizing, Deploying, and Maintaining Enterprise-class Node.js Applications, we share advanced techniques for launching and running enterprise-class products, services, and brand building for Node.js.

In our view, this is a subject that has not received the attention and expert insight it deserves. In most cases, the post-release process is longer and more impactful than the development process. This phase also determines whether node.js applications succeed or fail in delivering the business value promised by the technology.

EBook provides a practical basis for success in the critical first three months of Node.js’s successful launch — a time span from pre-production planning to continuous deployment and testing.

Specifically, the eBook provides tips, tricks, and best practices for each of the following key points:

1. Preparing for product launch:

Preparing for release is always a key point in any application development process, and the Same is true for node.js projects. This is your team’s last chance to find and fix problems before they affect your deployment process, end users, or the business itself.

The EBook guides users through the pre-launch process and highlights the following:

  • Optimize your code
  • Best practices for exception handling
  • Make sure your code meets security requirements
  • Configuring the Production Environment
  • Deployment considerations

When it comes to code optimization, there is a process called “linting.” among the best practices detailed in eBook pre-production. This requires running an automated code quality tool — such as ESLint or JShint — from the code base. It usually deals with very basic quality issues, but the point is that it catches avoidable — and very easy to fix — errors before putting your application in a dangerous situation.

2. The first 24 hours after node.js is deployed

After covering the fundamentals of an effective pre-production workflow, we’ll look at what to expect in the first 24 hours after deployment and how to respond.

Deploying enterprise applications can be painful. After all, XebiaLabs’ application release automation survey trends show that nearly 30% of application deployments fail. At the same time, trends in automated operations, continuous delivery, and automated release of applications show that 77% of organizations have problems with spontaneous production release. Obviously, anyone responsible for deploying an application should be prepared for errors — which could be recurring or occasional.

While a robust pre-production process can help minimize the impact of bugs, configuration failures, and other avoidable problems, professional Node.js developers should know how to locate common “day one” deployment issues — especially those that cause crashes or high impact.

Typical problems that may occur in the first 24 hours include:

  • The Node.js process crashes
  • The API call frequency limit is exceeded
  • Resolve WebSocket issues
  • Depend on the problem
  • File upload problem
  • DDoS attack

The good news on top of these (and some surprises) day one is that you’ll learn more about building better Node.js applications and how to deploy them with the fewest deployment problems. There will be problems later, but there will be fewer and fewer really serious ones.

The better news is that once you’ve effectively solved the problems of day one, you’ll be dealing with a much more stable and reliable application later on. This in turn allows you to focus on how to improve the performance of your application and how to upgrade your own process for building, testing, and deploying Node.js applications.

3. Continuous management

Having successfully deployed, the final chapter of eBook focuses on ongoing management of Node.js applications. While this is no different from any other application release process, there are a few details you should be aware of:

  • Memory leaks
  • Manage node.js concurrency
  • monitoring

As we discussed in eBook, application performance Monitoring (APM) is critical to maintaining the stability of application deployments and detecting sensitive regressions that can cause an application to slow down or fail outright if unchecked. APM solutions like AppDynamics can provide end-to-end insight into application behavior and provide specific monitoring capabilities for the Node.js stack.

Access to guide

Read all the best practices for deploying and managing your application in our latest eBook Advanced Node.js: Optimizing, Deploying, and Maintaining Enterprise Node.js Applications.

Download the Forrester Report to learn about the cost savings and business benefits you can expect from AppDynamics APM and its integration with Cisco technology.

If you find any mistakes in your translation or other areas that need to be improved, you are welcome to the Nuggets Translation Program to revise and PR your translation, and you can also get the corresponding reward points. The permanent link to this article at the beginning of this article is the MarkDown link to this article on GitHub.

The Nuggets Translation Project is a community that translates quality Internet technical articles from English sharing articles on nuggets. The content covers Android, iOS, front-end, back-end, blockchain, products, design, artificial intelligence and other fields. If you want to see more high-quality translation, please continue to pay attention to the Translation plan of Digging Gold, the official Weibo, Zhihu column.