In the previous two years we covered best practices for writing and operating Node.js applications (read the 2016 edition & 2017 edition). Another year has passed, so it’s time to revisit the topic of becoming a better developer!
In this article, we collected a few tips that we think Node.js developers should follow in 2018. Feel free to pick some development related New Year’s resolutions!
Tip #1: Use async - await
Async — await landed in Node.js 8 with a boom. It changed how we handle async events and simplified previously mind-boggling code bases. If you are not yet using async - await read our introductory blog post.
Refreshing your knowledge about old school async programming and Promises may also help.
Tip #2: Get acquainted with import and import()
ES modules are already widely used with transpilers or the @std/esm library. They are natively supported since Node.js 8.5 behind the --experimental-modules flag, but there is still a long way until they become production ready.
We suggest you to learn the foundations now and follow the progress in 2018. You can find a simple ES modules tutorial with Node.js here.
Tip #3: Get familiar with HTTP/2
HTTP/2 is available since Node.js 8.8 without a flag. It has server push and multiplexing, which paves the way for efficient native module loading in browsers. Some frameworks — like Koa and Hapi — partially support it. Others — like Express and Meteor — are working on the support.
HTTP/2 is still experimental in Node.js, but we expect 2018 to bring wide adoption with a lot of new libraries. You can learn more about the topic in our HTTP/2 blog post.
Tip #4: Get rid of code style controversies
Prettier was a big hit in 2017. It is an opinionated code formatter, which formats your code instead of simple code style warnings. There are still code quality errors — such as no-unused-vars and no-implicit-globals — that can not be automatically reformatted.
The bottom line is, that you should use Prettier together with your good old fashioned linter in your upcoming projects. It helps a lot, especially if you have people with dyslexia in your team.
Tip #5: Secure your Node.js applications
There are big security breaches and newly found vulnerabilities every year, and 2017 was no exception. Security is a rapidly changing topic, which can not be ignored. To get started with Node.js security, read our Node.js Security Checklist.
Tip #6: Embrace microservices
If you have deployment issues or upcoming large-scale projects, it may be time to embrace the microservices architecture. Learn these two techs to stay up to date in 2018’s microservices scene.
Docker is a software technology providing containers, which wrap up a piece of software in a complete filesystem that contains everything it needs to run: code, runtime, system tools and system libraries.Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications.
Before getting too deep into containers and orchestration, you can warm up by improving your existing code. Follow the 12-factor app methodology, and you will have a much easier time containerizing and deploying your services.
Tip #7: Monitor your services
Fix issues before your users even notice them. Monitoring and alerting is a crucial part of production deployment, but taming a complex microservice system is no easy feat. Luckily this is a rapidly evolving field, with ever-improving tools. Check out what the future of monitoring holds or learn about the recent OpenTracing standard.
If you are a more practical person our Prometheus tutorial gives a nice intro to the world of monitoring.
Tip #8: Contribute to open-source projects
Do you have some favorite Node.js projects? Chances are that they could use your help to become even better. Just find an issue that matches your interest and jump into coding.
What’s your Node.js Development advice?
What else would you recommend to your fellow Node.js developers to get right in 2018? Leave your opinion in the comments section!
We hope that you will have an awesome 2018. Happy coding!
Originally published at blog.risingstack.com on January 9, 2018.