Michael Dawson

Node.js lead for Red Hat and IBM

Michael Dawson

Michael Dawson is an active contributor to the Node.js project and chair of the Node.js Technical Steering Committee(TSC). He contributes to a broad range of community efforts including platform support, build infrastructure, N-API, Release, as well as tools to help the community achieve quality with speed (ex: ci jobs, benchmarking and code coverage reporting). As the Node.js lead for Red Hat and IBM , he works with Red Hat's and IBM's internal teams to plan and facilitate their contributions to Node.js and v8 within the Node and Google communities.Past experience includes building IBM's Java runtime, building and operating client facing e-commerce applications, building PKI and symmetric based crypto solutions as well as a number of varied consulting engagements. In his spare time, he uses Node.js to automate his home and life for fun.

Michael Dawson's contributions

Content for Node.js developers at NearForm event
Article

Best of NodeConf Remote: The 30-second review

Lucas Holmquist +2

Get the NodeConf Remote 2021 highlights, including the Node-RAPIDS machine learning framework, cloud-native Node.js development on Kubernetes, and more.

Node.js reference architecture
Article

NodeConf Remote 2021 preview: 4 must-see talks

Michael Dawson

Hear from Red Hat's Node.js and JavaScript experts at NodeConf Remote 2021, with talks on building cloud-native solutions on Kubernetes and more.

Node.js reference architecture
Article

How to build good containers in Node.js

Michael Dawson

Explore Node.js best practices for building good containers with faster development cycles and better deployments.

Node.JS on OpenShift 2
Article

Join the Red Hat team at OpenJS World 2021

Michael Dawson

Look back at Red Hat's involvement at the OpenJS World 2021 conference. We took part in sessions exploring the impact of Node.js and JavaScript on technology.

Node.js reference architecture
Article

Our advice for the best Node.js logging tool

Michael Dawson +1

Part 2 dives into best practices for Node.js logging, what makes a good logging tool, and which logger the Node.js reference architecture recommends.