Continuing on from Part One where we went through a brief history of containers and Kubernetes then Dockerized a NodeJS application, now we are ready to deploy to Kubernetes. If this is your first or nth time deploying to Kubernetes, Shipa makes this simple. You don’t have to worry about authoring multiple Kubernetes manifests and templates to deploy your application, all you need is an image.

Since its introduction in 2014 to the world, Kubernetes has been helping usher in the next generation of distributed workloads. As workloads started to be containerized, so did the need to manage the containers, thus the inception of container orchestrators. There have been a few container orchestrators out there before Kubernetes such as Docker Swarm and Apache Mesos. Though as a feature developer, Kubernetes can certainly feel like an 800-pound gorilla in the room.

Choosing a JavaScript framework for a new project can be a daunting task. There’s always a new one getting hype from the community, while the established players still have a lot to offer. So you need to do your homework and make sure the framework you choose is the right one for your specific requirements. Popularity alone is never the best indicator, but a review of the most widely-used options should help you decide which way to go.

JavaScript mutators shine among the improvements in Sensu Go 6.5 – they are both more effective and more efficient at transforming Sensu event data than pipe mutators. This post explores the advantages of JavaScript mutators and includes an example, but first, a brief review. In the Sensu observability pipeline, checks generate events, which Sensu then filters, transforms, and processes. A mutator is a component that transforms the event data.

Javascript execution analysis on dev environments is easy—just use Google Developer or some other free tools. However, getting the same level of analysis while your application is being used by a real user is much harder. You can’t possibly ask the end-user to help you troubleshoot. Even if you did, the user probably wouldn’t know what to do and they definitely wouldn’t be impressed by your organization.

This article was written by Nicolas Bohorquez and was originally published in The New Stack. Scroll below for the author’s picture and bio. Telegraf is the preferred way to collect data for InfluxDB. Though in some use cases, client libraries are better, such as when parsing a stream of server-side events. In this tutorial, you’ll learn how to read a data stream, store it as a time series into InfluxDB and run queries over the data using InfluxDB’s JavaScript client library.