DevOps.com

Where the world meets DevOps

  • Latest
    • Articles
    • Features
    • Most Read
    • News
    • News Releases
  • Topics
    • AI
    • Continuous Delivery
    • Continuous Testing
    • Cloud
    • Culture
    • DevSecOps
    • Enterprise DevOps
    • Leadership Suite
    • DevOps Practice
    • ROELBOB
    • DevOps Toolbox
    • IT as Code
  • DevOps Chats
  • Webinars
    • Upcoming
    • On-Demand Webinars
  • Library
  • Events
    • Virtual Summits
    • Conferences
  • Sponsored Communities
    • AWS Community Hub
    • CloudBees
    • IT as Code
    • Perforce DevSecOps
    • Rocket on DevOps.com
  • Related Sites
    • MediaOps
    • Container Journal
    • Security Boulevard
    • SweetCode.io
    • Digital Anarchist
    • DevOps TV on YouTube
    • DevOps Chat on SoundCloud
    • DevOps Connect
    • DevOps Dozen
  • Media Kit
  • Follow Us
    • Twitter
    • Google News
    • LinkedIn
    • Facebook
    • DevOps TV on YouTube
    • Email
  • AI
  • Cloud
  • Continuous Delivery
  • Continuous Testing
  • DevSecOps
  • Leadership Suite
  • Practices
  • ROELBOB
  • Low-Code/No-Code
  • IT as Code
  • More Topics
    • Application Performance Management/Monitoring
    • Culture
    • Enterprise DevOps

Home » Features » NodeSource Gets to the Source of the Node.js Issue

NodeSource Gets to the Source of the Node.js Issue

By: Mike Vizard on August 1, 2017 2 Comments

There’s no shortage of variants of Node.js in the world, but NodeSource is making a DevOps-related case for why IT organizations should standardize on its runtime implementation.

Recent Posts By Mike Vizard
  • Appian Extends Low-Code Approach to Aggregating Data
  • OpsRamp Extends AIOps Reach to Embrace Prometheus
  • CircleCI Acquires Vamp to Apply AI to CD
More from Mike Vizard
Related Posts
    Related Categories
  • Features
  • News
    Related Topics
  • application programming
  • developers
  • node.js
  • Node.js Foundation
  • nodesource
  • nsolid
  • programming language
Show more
Show less

NodeSource released version 2.3 of N|Solid, which adds support for event loop delay notifications that pinpoint precisely where an issue that needs to be addressed has occurred with an application, based on the Node.js variant of JavaScript.

Chris Krebs, former director of the U.S. Cybersecurity & Infrastructure Security Agency, discusses trying to uphold election integrity while battling disinformation during his fireside keynote chat at DevOpsConnect during @RSAC.

Pravin Halady, product manager for NodeSource, says N|Solid uniquely provides a runtime implementation of Node.js that provides that capability. Coupled with tools to monitor applications based on N|Solid, additional visualization tools and configurable webhooks-based integration to create alerts that can be shared via collaboration platforms such as Slack, N|Solid is the only Node.js runtime specifically optimized for enterprise IT environments, Halady says.

He notes one of the thornier issues organizations that embrace Node.js face is that any long-term synchronous activity blocking the event loop can prevent other incoming requests from reaching the server. Before too long, the application hangs or simply crashes. By providing insights into when an event loop delay is occurring in real time, Halady says IT organizations don’t have to waste time trying to reproduce the problem. The result is a much faster time to resolution of Node.js application issues.

DevOps teams can find themselves dealing with those types of issues at a much higher level of frequency once developers employ Node.js. As adoption of the most widely employed variant of JavaScript increases, IT organizations are managing more applications than ever. In fact, a recent survey published by the Node.js Foundation finds that three out four respondents plan to increase their usage of Node.js over the next 12 months. The primary reasons cited for that additional usage are increased developer productivity (68 percent); improved developer satisfaction (65 percent); reduced development costs (58 percent); and increased application performance (50 percent). Nearly half the respondents (47 percent) working in enterprise IT organizations say they been using Node.js for more than three years. Over half the developers (58 percent), in contrast, report having more than 10 years of experience working with Node.js.

IT organizations generally have very little visibility into what’s occurring inside Node.js applications, which makes it difficult to apply DevOps processes. In fact, most DevOps processes in place today are wrapped around applications written in more mature languages such as Java. Developers employing JavaScript tend to not be as well-versed in the role programmers ideally play within the context of an integrated set of DevOps processes.

In the absence of those processes, having the tools needed to debug an application in real time becomes more important to an IT operations teams that needs to inform a developer about the root cause of a specific issue. Otherwise, the developer ends up running one test after another in the hopes of replicating the problem. Unfortunately, the probability of accomplishing that goal inside most organizations is often relatively low. Because of that issue alone, an event loop delay notification made in real time is likely to pay for itself in a matter of hours.

— Mike Vizard

Filed Under: Features, News Tagged With: application programming, developers, node.js, Node.js Foundation, nodesource, nsolid, programming language

Sponsored Content
Featured eBook
The State of the CI/CD/ARA Market: Convergence

The State of the CI/CD/ARA Market: Convergence

The entire CI/CD/ARA market has been in flux almost since its inception. No sooner did we find a solution to a given problem than a better idea came along. The level of change has been intensified by increasing use, which has driven changes to underlying tools. Changes in infrastructure, such ... Read More
« 4 Ways to Give DevOps Teams the Support They Need
In Determining DevOps issues, Sometimes It’s the Process »

TechStrong TV – Live

Watch latest episodes and shows
christopher-krebs-rsa-conference

Upcoming Webinars

How Worldpay Protects Cardholder Data with Sysdig & Red Hat OpenShift
Wednesday, May 12, 2021 - 1:00 pm EDT
Is IAST the Next Big Thing in AppSec?
Thursday, May 13, 2021 - 1:00 pm EDT
Branch Disrupting the Insurance Market with Tyk API Management and GraphQL
Thursday, May 13, 2021 - 3:00 pm EDT

Top Stories of the Week

  • View DevOps.com Privacy Policy

Upcoming Webinars

Wed 12

Never Should You Ever in Kubernetes

Wed, May 12, 11:00 am - 12:00 pm EDT
Wed 12

How Worldpay Protects Cardholder Data with Sysdig & Red Hat OpenShift

Wed, May 12, 1:00 pm - 2:00 pm EDT
Thu 13

Is IAST the Next Big Thing in AppSec?

Thu, May 13, 1:00 pm - 2:00 pm EDT

More Webinars

Past Webinars

Latest from DevOps.com

What Data Catalogs Don’t Reveal
May 12, 2021 | Shevek
Consider Telemetry When Rearchitecting Applications
May 12, 2021 | Stephen Withers
SecDevOps is the Solution to Cybersecurity
May 12, 2021 | Marc Hornbeek
Appian Extends Low-Code Approach to Aggregating Data
May 11, 2021 | Mike Vizard
OpsRamp Extends AIOps Reach to Embrace Prometheus
May 11, 2021 | Mike Vizard

Most Read on DevOps.com

Empowering Developers Through Lean Code
May 7, 2021 | Gleb Polyakov
The Basics of DevSecOps Adoption
May 7, 2021 | Pavan Belagatti
How IT Ops Can Exceed Service Level Objectives in Digital Tr...
May 7, 2021 | Isaac Sacolick
Seven Reasons You Shouldn’t Hire a DevOps Engineer
May 11, 2021 | Bill Doerrfeld
Why You Must Lead With AI
May 7, 2021 | Alyssa Rochwerger

On-Demand Webinars

DevOps.com Webinar ReplaysDevOps.com Webinar Replays

Download Free eBook

The 101 of Continuous Software Delivery
New call-to-action
  • Home
  • About DevOps.com
  • Meet our Authors
  • Write for DevOps.com
  • Media Kit
  • Sponsor Info
  • Copyright
  • TOS
  • Privacy Policy

© 2021 ·MediaOps Inc.All rights reserved.

Our website uses cookies. By continuing to browse the website you are agreeing to our use of cookies. For more information on how we use cookies and how you can disable them, please read our Privacy Policy.