Lucas Holmquist

Sr. Software Engineer

Lucas is a Sr. Software Engineer at Red Hat. He is focused on the Node.js developer experience on Openshift as part of the Nodeshift Project.

While he is not a Node.js expert, He does pretend to be one at work.
 

Lucas Holmquist Profile pic

Articles by

Article

Node.js serverless functions on Red Hat OpenShift, Part 2: Debugging locally

Learn how to run and debug Node.js applications locally with Visual Studio Code, in Part 2 of this series on Node.js serverless functions.

Article

Node.js serverless functions on Red Hat OpenShift, Part 1: Logging

Take a deep dive into Node.js serverless functions! In Part 1, learn how logging works and how to customize a Node.js function application’s log levels.

Article

Introduction to the Node.js reference architecture, Part 3: Code consistency

Find out why code consistency matters in the Node.js reference architecture, and how to automate using linter tools like ESLint in your JavaScript projects.

Article

Fail fast with Opossum circuit breaker in Node.js

Don't let a single failing microservice bring down your entire system. Find out how the Opossum circuit breaker module for Node.js can help!

Article

An introduction to JavaScript SDK for CloudEvents

Get started with the JavaScript SKD for CloudEvents, a specification for describing event data for interoperability across services, platforms, and systems.

Article

Deploying Node.js applications to Kubernetes with Nodeshift and Minikube

See for yourself why Nodeshift is a great tool for developing against a Red Hat OpenShift cluster with the Source-to-Image (S2I) workflow.

Article

Introduction to the Node.js reference architecture, Part 1: Overview

Get to know the Node.js reference architecture with this new series. This article explains why we believe we need a Node.js reference architecture.

Article

Add standardized support information to your Node.js modules

Learn how the Nodeshift team added standardized support information to their Node.js modules, then get started with the tools and best practices they used.