Using minikube for Local Node.js Development

Troy Connor, Cloud Software Developer for CloudReach talks about Kubernetes in the background of Node.js development
27 October 2017   2920

Learning Kubernetes is hard. Learning how to set up Kubernetes even harder. Developers have to provision a cluster from a cloud provider and have to start paying for that immediately. This can discourage developers who want to build scalable microservices. On big teams, usually, developers have a DevOps team who can take care of scalability and optimization.

When breaking apart monolithic applications, microservices will have to scale to handle the load of the incoming requests. As the application grows, so will the need for the microservices. When developing their applications, developers can run into the problem where it doesn’t work in different environments. The phrase “It works on my machine” points fingers at a bigger problem. Developers can find this frustrating and it slows down updates to the application. The developer’s workflow can prevent this by using minikube.

For large enterprise applications who use the cloud as their platform, Kubernetes has been one of the many solutions to these issues. Quickly deploy, scale, and modernize your microservices with simple commands. Minikube allows you to test this functionality without the cloud provider. As a NodeJS developer, having the functionality to develop a workflow that you would use for your production application is very valuable.

In this talk we will discuss what Kubernetes is, we will discuss the advantages of using minikube, and we will show the functionality of what Kubernetes can do with NodeJS. We will show how to scale your application, how to deploy multiple copies of your application based on metrics, and show how to master blue/green deployments to not lose any uptime during updating your application.

Node.js v12.0.0 to be Rolled Out

It has giant list of updates, improvements and changes
24 April 2019   135

The release of Node.js 12.0.0, a platform for executing network applications in JavaScript, is available. Node.js 12.0 refers to branches with a long period of support, but this status will be assigned only in October, after stabilization. Updates for LTS branches are issued for 3 years. Support for the last LTS branch of Node.js 10.0 will last until April 2021, and the year before last LTS-branch 8.0 until January 2020. Support for the intermediate branch Node.js 11.0 will be discontinued in June 2019. The lifetime of the LTS branch 6.0 will end on April 30.

These are some of the large list of updates and new staff:

  • V8 engine was updated to version 7.4 with support for asynchronous stack traces, increasing await performance, parsing JavaScript and calls when the actual and declared number of arguments does not match;
  • TLS 1.3 is now supported in the tls module and TLS 1.0 / 1.1 is shutdown by default;
  • Enhancing protection and checks on the size of allocated memory in the Buffer class;

Get more info at official website.