Skip to main content
Category

Blog

Spring Forward With 50% Savings on Linux Foundation Training & Certification

By Blog, Training

We know there’s a lot happening in the world right now. To help make at least one thing a little easier, Linux Foundation Training & Certification is offering discounted pricing on all our offerings, including training courses, certification exams, bundles and bootcamps for one week. This offer reflects the best sitewide pricing of the year outside of Cyber Monday!

This is a perfect opportunity to grow your Node.js skills, whether you’re interested in Node.js Application Development (JSNAD) or Node.js Services Development (JSNSD) bundles.

Training bundles, plus certification, and bootcamps are 50% off, and standalone training courses and certification exams are 40% off. This offer ends April 19, and you can learn more here. 92% of hiring managers are struggling to find enough IT talent with skills in open source technologies, so this is your opportunity to kickstart a new career. If you don’t know where to start, take the Linux Foundation career path quiz, explore the IT career roadmap, or check out the new certification curriculum paths. Options include everything from system administration to engineering, cloud, web, blockchain, networking, hardware and many more!

OpenJS World Schedule Now Available

By Blog, OpenJS World

We’re excited to share the full OpenJS World schedule to date. View the daily schedule, including exciting breakout sessions and keynotes. You can also log in or sign up to sync your favorite sessions on your phone or calendar: https://events.linuxfoundation.org/openjs-world/program/schedule/

This year we’re joining cdCON to provide two great open source conferences in one ticket, June 6-10, 2022, in Austin, Texas. Discover, learn, and connect with those working on open source application development and deployment. Learn about the latest JavaScript technologies, check out new continuous delivery approaches and projects, and hear from inspiring tech leaders. 

Our planning committee is still working on scheduling presentations by your favorite open source project leaders at OpenJS. So stay tuned for more to come!

Highlights

Monday, June 6: Node.js training session led by Matteo Collina. NativeScript training with Nathan Walker and Alex Ziskind.

Tuesday, June 7: OpenJS Foundation keynotes, JavaScriptLandia community awards recognition, awesome breakout sessions!

Wednesday, June 8:  More exciting keynote speakers, including Cory Doctorow (@doctorow), Feross Aboukhadijeh (@feross), Brian Behlendorf (@brianbehlendorf), Myles Borins (@MylesBorins), Matteo Collina (@matteocollina), Reginé Gilbert (@reg_inee), Robin Ginn (@rginn206), Felienne Hermans (@felienne), Michael Jennings, Maggie Johnson-Pint (@maggiepint), Michaela Laurencin, and Rachel Nabors (@rachelnabors). 

Plus breakout sessions, yoga, and live band karaoke.

Thursday, June 9 and Friday, June 10: Project + Collab Summits 

Visit the event website to learn more and register today. Early bird pricing ends April 15, 2022!

Insights from the 2022 Fastify Survey

By Blog, Fastify, Project Updates

Survey finds web framework for Node.js is fast and performant

After the challenges that so many have faced the last few years, we really appreciate that so many Fastify users found the time to complete this survey. Fastify is a web framework for Node.js to help increase web performance, and is hosted by the OpenJS Foundation. Our community is everything, and getting feedback like this helps us to maintain and improve Fastify.

We had 108 respondents participate in this year’s survey, and surprising to no one,  the majority work in software or development, or are studying in those areas.

Most respondents found Fastify through GitHub, where Fastify’s repos reside. It is encouraging to see that Fastify is also being discovered through other mediums, which indicates a growing awareness of Fastify that will hopefully lead to more adoption and activity around the framework!

Where Fastify Excels

As the name of the framework implies, Fastify is fast and performant. Respondents overwhelmingly cited this as the reason why they enjoy using Fastify in their projects. Other positives included:

  • Active development and community
  • Documentation
  • Ease-of-use and simplicity
  • Growing plugin ecosystem
  • Support for modern JavaScript features
  • TypeScript support
  • Matteo Collina’s involvement as lead maintainer

These helpful features and benefits have been the result of years of work by maintainers and contributors alike, so we’d like to extend a big thank you to everyone who has been involved with Fastify! Also, thanks to Matteo Collina (Twitter: @matteocollina) for being so charming that he brings all the users to the yard.

Respondents also indicated a high level of satisfaction with Fastify across the board:

Where Fastify Can Improve

We know that “perfection isn’t attainable but if we pursue it we can attain excellence.”  So we asked what improvements users would like to see in future releases.

Requests for additional TypeScript support far outweighed any other, with requests for more examples and clarity in documentation ranking second in priority. 75% of respondents stated they use TypeScript, so this is not surprising!

V4 of Fastify resolves some of these grievances, with new automatic types for query strings and bodies, fixes for missing types, typed decorators, and more. One of the responses requested support for hot reloading, which is currently being explored through tooling like restartable!

The overall sentiment of this feedback has been positive. As Fastify progresses into V4 and beyond we hope that we can remove pain points in Fastify that users have highlighted in their responses, whilst continuing to provide the high-performance users have come to expect!

Many thanks to Alix Robinson and Matteo Collina for preparing the survey. This article was brought to you by Frazer Smith.

OpenJS In Action: Betting Your Product’s Developer Experience on Node.js and Open Source

By Blog, OpenJS In Action, Uncategorized

OpenJS recently spoke with Yavor Georgiev, Co-Founder, and Head of Product at Fusebit, to learn more about how his product leverages Node.js and other benefits of the open source ecosystem. Fusebit prides itself on being a “developer-first” focused product that takes the pain out of implementing SaaS integrations. Yavor and one of his co-founders at Fusebit previously had worked at Microsoft specifically on bringing support for Node.js to the Azure Cloud. 

We learned that the Fusebit product team strongly believes in and supports the Node.js ecosystem. The entire Fusebit service is based on a “JavaScript developer experience with Node.js and npm”, which delivers a best-in-class experience for their customers.

Programming Model Based on Node.js

The Fusebit service exposes a programming model based on Node.js, allowing any developer to create an integration. That’s key for a couple of reasons. First, since there’s already a massive community of developers familiar with Node.js and JavaScript, developers don’t have to learn anything new and can use their existing processes and DevOps techniques. Another key benefit to having their model based on Node.js is that due to the size of the npm ecosystem, there’s a module for virtually everything. One of the benefits of open source is that developers don’t have to write and implement everything from scratch. In this case, they can grab a module from npm and speed up their productivity. 

Security

We touched on the issue of security. Two of the co-founders of Fusebit were previously employees at Microsoft and later at Auth0, an identity and access management platform on which Fusebit’s security is based. Were it not for Node.js and companies like Auth0 being invested in securing the open source ecosystem, the Fusebit product itself wouldn’t be where it is today. They also leverage modules from npm where developers constantly update code and patch vulnerabilities.

Stripe for SaaS Integrations

The Fusebit service is like “Stripe for SaaS integrations.” So if you’re a developer working on a SaaS application and you need integrations to third-party SaaS products like Slack or JIRA, Fusebit provides the integrations in a turnkey way. Based on Node.js, there’s an infinite ability to customize solutions. As a result, Fusebit achieves great problem-solution-fits for their customers, unlike some low-code and no-code solutions. Another reason their product is focused on a developer audience is data fidelity is essential when connecting business software to something like Salesforce or other SaaS products. Someone has to have the right technical mindset to create that type of integration.

Open Source Contributions

The Fusebit team is also a proud contributor to open source development. Most of their source code is available on GitHub, so customers can go in and fork features, SaaS connectors, etc., and make them their own. 
We talked about everynode, a new project that Fusebit recently contributed to the open source ecosystem that lets developers run any version of Node.js, including the most recent builds on AWS Lambda. Lambda sometimes doesn’t have the latest versions available. The Fusebit team initially built it internally for integrations that required newer versions of Node.js and needed to run on AWS.

“You know, selfishly, it’s actually better for more developers to be familiar with it instead of keeping it secret. The more people are familiar with aspects of Fusebit that we’ve made open source, the better for us.”

The Fusebit team routinely takes pieces of the Fusebit service and makes them available to the public, whether it’s npm packages, repositories, or other content. The team also contributes by filing issues and contributing fixes to OSS projects and Node.js itself when needed. On making parts of their code public, Yavor commented, “You know, selfishly, it’s actually better for more developers to be familiar with it instead of keeping it secret. The more people are familiar with aspects of Fusebit that we’ve made open source, the better for us.”

JavaScript FTW!

With so many other programming languages out there, Yavor believes JavaScript is still in the lead for many reasons. It’s amazingly versatile, giving devs the ability to build end-to-end solutions. The language itself continues to evolve, and there are some remarkable initiatives around the standardization of the module spec, for example. Now you can write a module and use it pretty much anywhere JavaScript runs, whether it’s Node.js or in a browser. This continuous innovation supports the JavaScript language and the community and encourages people to continue learning JavaScript. 

Fusebit thanks the Node.js community and everybody who’s contributing unpaid hours to make Node.js and the package ecosystem great. According to Yavor, the Node.js community has been a tremendous help to their product. They also give back to our community by hiring folks with Node.js in their skillset. 

We at the OpenJS Foundation appreciate Yavor sharing his thoughts and experience.

Watch the Interview

Q & A with Alex Liu, OpenJS Board Member and Engineering Manager at Netflix

By Blog, member blog
Alex Liu

We talked with our recently re-elected board member from Netflix Alex Liu about his new position as OpenJS End-User Board Director and learned more about how Netflix finds value in the OpenJS Foundation. Alex represents the many end-users or organizations using JavaScript technologies to build their products and services.

In addition to the End-User Board seat, Netflix is a Gold member of the OpenJS Foundation. Each Platinum member is entitled to appoint one Director to the board, and Gold and Silver members vote to select their representatives. The board also includes community representation, with two Community Director positions elected.

Alex is the Engineering Manager for the Node.js Platform team at Netflix, responsible for curating the Node.js development experience for hundreds of engineers across the company. His team builds on the shoulders of the incredible open source communities that have found a home in the OpenJS Foundation and advocates for the continued support and sustainability of the vibrant communities that have made today’s ecosystem possible.

Using a serverless Node.js platform, you and your team at Netflix curate a complete end-to-end development environment for Netflix engineers who are creating, developing, and deploying Node.js services. How does being on the OpenJS Foundation board help your work at Netflix?

Being a part of the OpenJS Foundation has opened opportunities for collaboration and information sharing. We now have a better understanding of how Node.js is growing within the industry and how Netflix can play a meaningful part in that story. The deeper engagement goes two ways; it allows us to learn from the community and enables us to share unique challenges with our peers.

Within Netflix, Node.js traditionally focuses on server-side use cases separate from the larger front-end JavaScript space, but we leave a lot on the table by not exploring how we can bridge that gap. For many of our engineers building web applications and Node.js services go hand-in-hand and that mindset must be adopted to provide a more holistic development experience for our teams. Additionally, we have JavaScript use cases that are outside of the traditional browser experience. For example, the Netflix TV application experience is a JavaScript UI running on a native SDK, which brings a set of unique challenges. It’s a win / win for both sides as we look to share and grow together with the OpenJS foundation.

Node.js v18 will be released April 18. How does Netflix evaluate new releases of Node.js?

Similar to how AWS raised the abstraction bar for hardware management in the early cloud days, we’re raising the abstraction bar for service development. 

My team owns and operates a managed platform, “NodeQuark”, for Node.js services at Netflix. The mission of the platform is to provide not only the Node.js runtime, but all the integrations needed to hit the ground running in the Netflix ecosystem in a transparent manner. NodeQuark tracks Node.js LTS releases, and the managed architecture allows us to seamlessly test, validate, canary, and ship updates to both the Node.js runtime and our ecosystem integrations without having to involve our customers. Our platform customers need only bring their business logic. 

We do have scenarios requiring more traditional services that are not built on NodeQuark, where service owners are responsible for their entire stack, including evaluating new Node.js releases on their own cadence. In the future we will continue to explore these use cases more thoroughly to support them within NodeQuark.

As part of the OpenJS board, what do you hope to accomplish in 2022?

I’ve been discussing goals for the board with Robin Ginn, our Executive Director. Fundamentally, I want to build better relationships with people engaged with the foundation. Why are you showing up? What keeps you engaged? How is that benefiting you and your company? Better understanding these types of benefits and motivations will help the Foundation better support our members. And that will lead to eventual growth and further investment in the success of the Foundation.

What advice would you offer others wanting to get involved with the Foundation?

I’ve had the privilege of getting involved through Netflix. For individuals who want to share their experience, there is JavaScriptLandia. This is designed to be a part of the community where individual contributors can join and fully engage. My biggest piece of advice is to reach out, say hello, find out what the OpenJS Foundation is up to lately. I’m confident you’ll find a fun and engaging way to join our community!

OpenJS In Action: How Wix Applied Multi-threading to Node.js and Cut Thousands of SSR Pods and Money

By Blog, Case Study, OpenJS In Action
Author: Guy Treger, Sr. Software Engineer, Viewer-Server team, Wix

Background:

In Wix, as part of our sites’ Server-Side-Rendering architecture, we build and maintain the heavily used Server-Side-Rendering-Execution platform (aka SSRE). 

SSRE is a Node.js based multipurpose code execution platform, that’s used for executing React.js code written by front-end developers all across the company. Most often, these pieces of JS code perform CPU-intensive operations that simulate activities related to site rendering in the browser.

Pain: 

SSRE has reached a total traffic of about 1 million RPM, requiring at times largely more than accepted  production Kubernetes pods to serve it properly. 

This made us face an inherent painful mismatch:
On one side, the nature of Node.js – an environment best-suited for running I/O-bound operations on its single-threaded event loop. On the other, the extremely high traffic of CPU oriented tasks that we had to handle as part rendering sites on the server.

The naive solution we started with clearly proved inefficient, causing some ever growing pains in Wix’s server and infrastructure, such as having to manage tens of thousands of production kubernetes pods.

Solution: 

We had to change something. The way things were, all of our heavy CPU work was done by a single thread in Node.js. The straightforward thing that comes to mind is: offload the work to other compute units (processes/threads) that can run parallely on hardware that includes multiple CPU cores.

Node.js already offers multi-processing capabilities, but for our needs this was an overkill. We needed a lighter solution that would introduce less overhead, both in terms of resources required and in overall maintenance and orchestration.

Only recently, Node.js has introduced what it calls worker-threads. This feature has become Stable in the v14 (LTS) released in Oct 2020.

From the Node.js Worker-Threads documentation:

The worker_threads module enables the use of threads that execute JavaScript in parallel. To access it:

const worker = require(‘worker_threads’);

Workers (threads) are useful for performing CPU-intensive JavaScript operations. They do not help much with I/O-intensive work. The Node.js built-in asynchronous I/O operations are more efficient than Workers can be.

Unlike child_process or cluster, worker_threads can share memory.

So Node.js offers a native support for threading that we could use, but since it’s a pretty new thing around, it still lacks a bit in maturity and is not super smooth to use in your production-grade code of a critical application.

What we were mainly missing was:

  1. Task-pool capabilities
    What Node.js offers?
    One can manually spawn some Worker threads and maintain their lifecycle themselves. E.g.:
const { Worker } = require(“worker_threads”);

//Create a new worker
const worker = new Worker(“./worker.js”, {workerData: {….}});

worker.on(“exit”, exitCode => {
  console.log(exitCode);
});


We were reluctant to spawn our Workers manually, make sure there’s enough of them at every given time, re-create them when they die, implement different timeouts around their usage and more stuff that’s generally available for a multithreaded application.

  1. RPC-like inter-thread communication
    What Node.js offers?
    Out-of-the-box, threads can communicate between themselves (e.g. the main thread and its spawned workers) using an async messaging technique:
// Send a message to the worker
aWorker.postMessage({ someData: data })

// Listen for a message from the worker
aWorker.once(“message”, response => {
  console.log(response);
});

Dealing with messaging can really make the code much harder to read and maintain. We were looking for something friendlier, where one thread could asynchronously “call a method” on another thread and just receive back the result.

We went on to explore and test various OS packages around thread management and communication.


Along the way we found some packages that solve both the threadpool problem and the elegant RPC-like task execution on threads. A popular example was piscina. It looked all nice and dandy, but there was one showstopper. 


A critical requirement for us was to have a way for our worker threads to call some APIs exposed back on the main thread. One major use-case for that was reporting business metrics and logs from code running in the worker. Due to the way these things are widely done in Wix, we couldn’t directly do them from each of the workers, and had to go through the main thread.

So we dropped these good looking packages and looked for some different approaches. We realized that we couldn’t just take something off the shelf and plug it in.

Finally, we have reached our final setup with which we were happy.

We mixed and wired the native Workers API with two great OS packages:

  • generic-pool (npmjs) – a very solid and popular pooling API. This one helped us get our desired thread-pool feel.
  • comlink (npmjs) – a popular package mostly known for RPC-like communication in the browser (with the long-existing JS Web Workers). It recently added support for Node.js Workers. This package made inter-thread communication in our code look much more concise and elegant.

The way it now looks is now along the lines of the following:

import * as genericPool from ‘generic-pool’;
import * as Comlink from ‘comlink’;
import nodeEndpoint from ‘comlink/dist/umd/node-adapter’;

export const createThreadPool = ({
                                    workerPath,
                                    workerOptions,
                                    poolOptions,
                                }): Pool<OurWorkerThread> => {
    return genericPool.createPool(
        {
            create: () => {
                const worker = new Worker(workerPath, workerOptions);
                Comlink.expose({
                    …diagnosticApis,
                }, nodeEndpoint(worker));

                return {
                    worker,
                    workerApi: Comlink.wrap<ModuleExecutionWorkerApi>(nodeEndpoint(worker)) };
            },
            destroy: ({ worker }: OurWorkerThread) => worker.terminate(),
        },
        poolOptions
    );
};


And the usage in the web-server level:

const workerResponse = await workerPool.use(({ workerApi }: OurWorkerThread) =>
    workerApi.executeModule({
        …executionParamsFrom(incomingRequest)
    })
);

// … Do stuff with response

One major takeaway from the development journey was that imposing worker-threads on some existing code is by no means straightforward. Logic objects (i.e. JS functions) cannot be passed back and forth between threads, and so, sometimes considerable refactoring is needed. Clear concrete pure-data-based APIs for communication between the main thread and the workers must be defined and the code should be adjusted accordingly.

Results:

The results were amazing: we cut the number of pods by over 70% and made the entire system more stable and resilient. A direct consequence was cutting much of Wix’s infra costs accordingly.

Some numbers:

  • Our initial goal was achieved – total SSRE pod count dropped by ~70%.
    Respectively, RPM per pod improved by 153%.
  • Better SLA and a more stable application – 
    • Response time p50 : -11% 
    • Response time p95: -20%
    • Error rate decreased even further: 10x better
  • Big cut in total direct SSRE compute cost: -21%

Lessons learned and future planning:

We’ve learned that Node.js is indeed suitable also for CPU-bound high-throughput services. We managed to reduce our infra management overhead, but this modest goal turned out to be overshadowed by much more substantial gains.

The introduction of multithreading into the SSRE platform has opened the way for follow-up research of optimizations and improvements:

  • Finding the optimal number of CPU cores per machine, possibly allowing for non-constant size thread-pools.
  • Refactor the application to make workers do work that’s as pure CPU as possible.
  • Research memory sharing between threads to avoid a lot of large object cloning.
  • Apply this solution to other major Node.js-based applications in Wix.

OpenJS Foundation Names 2022  Board of Directors

By Blog

OpenJS Foundation is thrilled to welcome the newly elected 2022 Board of Directors, including our first-time Silver Board Director Jordan Harband from Coinbase. 

Jordan Harband, OpenJS Silver Director, Coinbase

Jordan joins the appointed Platinum Directors, the recently re-elected Gold and End-User Directors, and the Cross Project Council Directors who are elected by the technical communities at various times through the year. 

Meet our 2022 Board Directors:

  • Todd Moore, Platinum Director, IBM
  • Sonal Bhoraniya, Platinum Director, Google
  • Sean Johnson, Platinum Director, Joyent
  • Shayne Boyer, Platinum Director, Microsoft
  • Daniel Cousineau, Gold Director, GoDaddy
  • Jordan Harband, Silver Director, Coinbase
  • Alex Liu, End-User Director, Netflix
  • Sara Chipps, Cross Project Council Director
  • Michael Dawson, Cross Project Council Director

Jordan is an active member of the OpenJS Cross Project Council, the technical governing body of the OpenJS Foundation. He’s the maintainer for nvm (Node Version Manager), a widely-used OpenJS project to manage multiple versions of Node.js. Jordan also has been heavily involved in the Node.js project, and moderates the Node.js community Slack channel. He also is a longtime participant in TC39 (the committee that writes the specification for JavaScript) and was an editor of the specification from 2018-2021. He received an Ecma Recognition Award for his contributions as an Editor of the JavaScript language specification (ECMA-262). Jordan is an engineer at Coinbase and is helping build out its Open Source Programs office. Coinbase has 73+ million verified users and relies heavily on JavaScript and Node.js tooling for every user-facing client. The company also recently transitioned to a single React Native codebase for its mobile development. 

WIth this Board transition, we also want to extend a giant thank you to departing Silver Board Director Myles Borins, who remains very much a part of our OpenJS communities. His work at GitHub helps to make npm better and more secure for developers, and his contributions to TC39 and his leadership in helping build our open governance model has greatly influenced the positive culture we all share today at OpenJS.

Read more about our new faces who joined the Board last fall, Shayne Boyer at Microsoft, Daniel Cousineau at GoDaddy, and Alex Liu at Netflix

Node.js Trademarks Transferred to OpenJS Foundation

By Blog, Node.js

OpenJS Foundation had previously been granted free, perpetual license to use Node.js trademarks and logo for the past 6 years

SAN FRANCISCO – February 14, 2022 – The OpenJS Foundation, providing vendor-neutral support for sustained growth within the open source JavaScript community, is announcing acquisition of ownership of the Node.js logo trademarks. 

Effective immediately, the OpenJS Foundation will take on the ongoing management and maintenance of the Node.js trademarks. The ownership and stewardship of the Node.js trademarks has moved from Joyent to the OpenJS Foundation. The rules governing usage of the Node.js trademarks will now be consistent with all of the other OpenJS Foundation projects’ trademarks. For contributors, nothing will change. 

Node.js is an Impact Project hosted at the OpenJS Foundation. For the past six years, Joyent has granted the OpenJS Foundation (and the Node.js Foundation prior) a perpetual, free license to use the “Node.js” trademarks, including the Node.js hexagon graphic.

The Node.js Technical Steering Committee (TSC) responded to the news, “It’s great to see the Node.js trademarks move over to the OpenJS Foundation. It’s been a hope since the formation of the Foundation and we’re happy to see it become a reality. One of the advantages of Node.js being a project at the OpenJS Foundation is legal support including the management of things like trademarks to help protect the work of the broad range of collaborators.”

Trademarks are important to the protection and adoption of an open source project because they identify a specific source of the code. Our goal is to ensure that the OpenJS trademark policy is as flexible and easy to understand as legally possible, while assuring the quality of products or services using Node.js or other OpenJS projects’ brands

“The responsible stewardship of the Node.js project over the past decade has led to critical, widespread adoption. This stewardship and positive collaboration between Joyent and originally the Node.js Foundation, now the OpenJS Foundation, has helped overcome differences among the contributors and the code base,” said Robin Ginn, OpenJS Foundation Executive Director. “Joyent can confidently contribute its trademarks to the OpenJS Foundation as a place of stability and industry-wide collaboration.” 

“Joyent has long believed in the power of open source to create opportunities for developers and businesses, and it’s gratifying to see how Node.js underpins the economic growth for so many,” said Sung Whan Moon, President & COO, Joyent. “The OpenJS Foundation is the right place to house ownership of the Node.js trademarks. As Node.js moves into its second decade, having the trademarks in a neutral home, but with the ability to enact trademark restrictions if needed, fully ensures the integrity of the project.”

Node.js is a healthy community supported extensively by companies that have increased the scale and commercial adoption of this project, including Bloomberg, NASA, Netflix, and many more. Node.js just shipped Node.js 17 and moved Node.js 16 to Long Term Support (LTS).

“The OpenJS Foundation will make a good home for the Node.js trademarks. Joyent is a long-standing member of the OpenJS Foundation, and developers can continue to rely on Node.js and build high quality solutions and products,” said Sean Johnson, Head of Commercial Group, Joyent, and OpenJS Board Platinum Director. “The outlook for Node.js adoption is brighter than ever.”

“A big thank you to OpenJS Foundation member Joyent. They are an important community member of the Node.js ecosystem and have assisted in the stewardship of the Node.js trademarks for the past decade. This is a good progression forward, and bodes well for the next decade of Node.js development,” said Todd Moore, VP of Open Technology and Developer Advocacy at IBM, and OpenJS Foundation Board Chairperson. “The OpenJS Foundation is positioned well to pursue its mission of driving the broad adoption of JavaScript technologies and ongoing development of key Node.js solutions and related technologies.”

Work is well underway on the future of Node.js at the OpenJS Foundation, and Node.js continues to grow. The OpenJS Foundation staff and Cross Project Council (CPC) community technical leaders are working on security and diversity efforts and much more. The Node.js maintainers are working collaboratively on the strategic directions for Node.js over the coming decade. If you want to join this effort please see Node.js next-10 and join one of the projects teams or working groups.

OpenJS Resources

To learn more about how you could be a part of the OpenJS Foundation, click here.

About OpenJS Foundation

The OpenJS Foundation is committed to supporting the healthy growth of the JavaScript ecosystem and web technologies by providing a neutral organization to host and sustain projects, as well as collaboratively fund activities for the benefit of the community at large. The OpenJS Foundation is made up of 38 open source JavaScript projects including Appium, Dojo, jQuery, Node.js, and webpack and is supported by 30 corporate and end-user members, including GoDaddy, Google, IBM, Intel, Joyent, and Microsoft. These members recognize the interconnected nature of the JavaScript ecosystem and the importance of providing a central home for projects which represent significant shared value. 

About Linux Foundation

Founded in 2000, the Linux Foundation is supported by more than 1000 members and is the world’s leading home for collaboration on open source software, open standards, and open hardware. Linux Foundation projects like Linux, Kubernetes, Node.js and more are considered critical to the development of the world’s most important infrastructure. Its development methodology leverages established best practices and addresses the needs of contributors, users and solution providers to create sustainable models for open collaboration. For more information, please visit their website.

Media Contact

Jesse Casman

Story Changes Culture

jesse@storychangesculture.com

415-730-2793

Latest Node.js Savings End February 11, 2022

By Blog, Certification and Training, Node.js

It’s always a great time to invest in training or certification for you or your engineering team. The OpenJS Foundation, in partnership with the Linux Foundation, will be discounting all Node.js Certifications and Trainings up to 60% through Friday, February 11, 2022. Some of the world’s leading tech companies use the Node.js runtime in production and prefer to hire developers who are experienced with Node.js. The OpenJS Certification and Training program serves to help developers in their professional development goals.

Discounts Up to 60% with Code: NODE222 

OpenJS Node.js Services Developer Certification Exam (JSNSD) $375 $150

OpenJS Node.js Application Developer Certification Exam (JSNAD) $375 $150

Node.js Services Development Online Course + JSNSD Exam Bundle $575 $230

Node.js Application Development Online Course + JSNAD Exam Bundle $575 $230

POWER Bundle – JSNSD Course & Exam Bundle AND JSNAD Course and Exam Bundle $1150 $460

What’s included with certifications?

  • 12 month exam eligibility    
  • Free exam retake
  • Digital badge and PDF certificate upon passing

What’s included in online trainings?

  • Hands-on labs & assignments
  • Video content
  • 12 months of access to online courses
  • Discussion forums
  • Digital badge and PDF certificate upon completion

Certifications

Certifications are excellent ways to validate your own development skills to yourself, employers, and the world. 

OpenJS Node.js Application Developer (JSNAD)
The OpenJS Node.js Application Developer certification is ideal for the Node.js developer with at least two years of experience working with Node.js. For more information and how to enroll: https://training.linuxfoundation.org/certification/jsnad/

OpenJS Node.js Services Developer (JSNSD)
The OpenJS Node.js Services Developer certification is for the Node.js developer with at least two years of experience creating RESTful servers and services with Node.js. For more information and how to enroll: https://training.linuxfoundation.org/certification/jsnsd/

Training Offerings

Feel confident in taking your exams with the Node.js Training courses. These courses help prepare developers for the Node.js certification exams. 

Node.js Application Development (LFW211)
This course provides core skills for effectively harnessing a broad range of Node.js capabilities at depth, equipping you with rigorous skills and knowledge to build any kind of Node.js application or library. While by design the training content covers everything but HTTP and web frameworks, the crucial fundamentals presented prepares the student to work with web applications along with all types of Node.js applications.

Node.js Services Development (LFW212)
This course provides a deep dive into Node core HTTP clients and servers, web servers, RESTful services and web security essentials. With a major focus on Node.js services and security, this content is an essential counterpart to the Node.js Application Development (LFW211) course, and will prepare you for the OpenJS Node.js Services Developer (JSNSD) exam.

If you’d like to pursue Node.js Certifications and Trainings and this sounds like something you’d like to know more about, check out more information at this link.

Node.js in an Impact Project of the OpenJS Foundation.

Speakers List Announced for OpenJS World 2022

By Blog, OpenJS World

The OpenJS Foundation has announced the early list of Keynotes and Featured Speakers to date for OpenJS World 2022. This event will be held June 6-10, 2022, in Austin, Texas. Every year, OpenJS World gives developers, project managers, and decision-makers the ability to learn and engage directly with leaders building modern applications at a massive scale. Topics cover development, security, performance, automation & testing, community building, and more.

Join us this year at #OPENJSWORLD22 and help build the community! Register now!

This conference will be the first time in two years that in-person events will be an option for attendees. When registering, attendees decide whether it’s in person or virtual. It is also the first time the event will be co-located with CD Foundation’s cdCon, bringing a much broader range of open source topics in software delivery, DevOps, GraphQL, and more.

Brian Behlendorf was a primary developer of the Apache Web server, the most popular web server software on the Internet, and a founding member of the Apache Software Foundation.

Matteo Collina is Chief Software Architect at NearForm, a Node.js Technical Steering Committee member, and author of the fast logger Pino and the Fastify web framework. He is a seasoned international conference speaker, and he co-authored the “Node.js Cookbook Third Edition” edited by Packt.

Cory Doctorow is a blogger, journalist, and science fiction author, and served as co-editor of the blog Boing Boing. He is an activist in favor of liberalising copyright laws and a proponent of the Creative Commons organization.

Maggie Johnson-Pint, TPM, Stripe User Experiences. Maggie is an Engineering Manager in Azure SRE, an OpenJS Foundation representative to TC39, and a champion of Date of rework in Javascript. In addition, she is an active maintainer of Moment.js.

Rachel Nabors, Learning Community on React Core, Facebook. Rachel I builds and manages the React and React Native learning communities and educational materials at Facebook. She has a passion for creating spaces in which developers from all backgrounds want to participate.

Felienne Hermans is an associate professor at the Leiden Institute of Advanced Computer Science at Leiden University and works at the Vrije Universiteit Amsterdam, where she teaches prospective computer science teachers. She is a high-school CS teacher herself at Lyceum Kralingen. Felienne is the Hedy programming language creator and was one of the founders of the Joy of Coding conference.

Robin Bender Ginn is the Executive Director of the OpenJS Foundation, driving broad adoption and development of key JavaScript solutions and related technologies. Robin advances the Foundation’s mission to drive adoption and ensure sustainability in the JS and web development ecosystem.

David Mark Clements is a Principal Architect, technical author, public speaker, and OSS creator specializing in Node.js and browser JavaScript.

Jonathan Lipps is the architect and project lead for Appium, the popular open source automation framework, and the creator of Appium Pro, bringing fresh mobile testing tips to the world every week.

Nick O’Leary is the CTO and Founder of FlowForge Inc, where he is leading the OpenJS Node-RED project and building a low-code development platform.

Nathan Walker is a cofounder of nStudio and an active NativeScript Technical Steering Committee member with a passion for open source.

Alex Ziskind is the founder of NativeScripting, which offers rich video courses on a growing list of topics. He is also the founder of Nuvious, which services a diverse set of clients and software projects.