Below you can find RisingStack‘s collection of the most important Node.js news, projects & updates from this week:
This post focuses on building a simple microservice and packaging it in a docker container, then hosting the container on AWS.
Deploying microservices to the cloud is plagued with lots of complexity. To simply the microservice portion we’re going to use an NPM library called Hydra – which will greatly simply the effort while offering considerable scalability benefits. Even if you choose not to use Hydra, the information in this post should help you get started with AWS and Docker.
This article is about running and monitoring Node.js applications in Production.
Let’s discuss these topics:
- What is monitoring?
- What should be monitored?
- Open-source monitoring solutions
- SaaS and On-premise monitoring offerings
In case you missed it, Node now supports async/await out of the box since version 7.6.
Why Is It better?
- Concise and clean
- Error handling
- Intermediate values
- Error stacks
The growing number of Netflix subscribers – nearing 85 million at the time of this Node.js Interactive talk – has generated a number of scaling challenges for the company.
In his talk, Yunong Xiao, Principal Software Engineer at Netflix, describes these challenges and explains how the company went from delivering content to a global audience on an ever-growing number of platforms, to supporting all modern browsers, gaming consoles, smart TVs, and beyond.
Find out how to set up a continuous deployment pipeline with AWS ECS, AWS CloudFormation, Node.js, Docker, and Semaphore.
The end goal is to have a workflow that allows us to push code changes up to GitHub and have them seamlessly deployed on AWS ECS. To accomplish this, we’ll have Semaphore watch our GitHub repository, test it whenever changes are made, and deploy it if the branch being updated is master.
Capital One CIO Robert Alexander has encouraged the company’s IT department to operate like a startup and embrace open source software development.
The result has been several different project teams using Node.js to rapidly prototype and build new applications inside the business, cutting the time of the development cycle significantly and fostering a climate of innovation.
So it would appear that there is a memory leak in v4.8.1 and v6.10.1
Latest Node.js Releases
- do not segfault on out-of-range index
- Fix memory leak if certificate is revoked
- upgrade npm to 4.2.0
- fix async await desugaring in V8
- add option to stop duplicates in history
Previously in the Node.js Weekly Update
In the previous Node.js Weekly Update we read about the new LTS and Current versions, e2e testing with Nightwatch, and the free Orgs npm announced and more..