The microservices pattern is pretty standard for today’s software architecture. Microservices let you break up your application into small chunks and avoid having one giant monolith. The only problem is that if one of these services fails, it could have a cascading effect on your whole architecture.
Continue reading Fail fast with Opossum circuit breaker in Node.js
Continue reading Containerize and deploy Strapi applications on Kubernetes and Red Hat OpenShift
Red Hat is sponsoring the very first NearForm Presents event on Mar. 31, hosted by IBM. This online event will feature four talks on interesting topics related to Node.js Core, along with exciting workshop options.
Continue reading What’s coming for Node.js developers at NearForm event
A great thing about Node.js is how well it performs inside a container. With the shift to containerized deployments and environments comes extra complexity. One such complexity is observing what’s going on within your application and its resources, and when resource use is outside of the expected norms.
Continue reading Monitor Node.js applications on Red Hat OpenShift with Prometheus
In today’s world of serverless functions and microservices, events are everywhere. The problem is that they are described differently depending on the producer technology you use.
In a previous article, I showed how easy it was to deploy a Node.js application during development to Red Hat OpenShift using the Nodeshift command-line interface (CLI). In this article, we will take a look at using Nodeshift to deploy Node.js applications to vanilla Kubernetes—specifically, with Minikube.
Continue reading Deploying Node.js applications to Kubernetes with Nodeshift and Minikube
Welcome to this new series introducing the Node.js reference architecture from Red Hat and IBM. This article is an overview of our reasons for developing the Node.js reference architecture—both what we hope the architecture will offer our developer community and what we do not intend it to do. Future articles will offer a detailed look at different sections of the reference architecture.
Continue reading Introduction to the Node.js reference architecture, Part 1: Overview
Continue reading Making environment variables accessible in front-end containers
By default, most containers are run as the root user. It is much easier to install dependencies, edit files, and run processes on restricted ports when they run as root. As is usually the case in computer science, though, simplicity comes at a cost. In this case, containers run as root are more vulnerable to malicious code and attacks. To avoid those potential security gaps, Red Hat OpenShift won’t let you run containers as a root user. This restriction adds a layer of security and isolates the containers.