 If you'd like to learn a little bit more about Node.js, why you should be using it, why it's interesting and what Red Hat is doing in the Node.js ecosystem, then you've come to the right place. Node.js is a runtime that lets you run JavaScript outside the browser. We've all used JavaScript in the browser as it's part of almost every web application that's out there. But Node.js unlocks the ability to run JavaScript both on the front and the back end, using the same language across the full application. This leads to some great productivity benefits, and along with the great performance that you can get in certain situations has really led to its popularity and growth over the last few years. If we look at a little bit of the data that's out there, we can see from GitHub that JavaScript has been and is one of the most used languages in terms of the repositories that are out there. If we also look at the module ecosystems, we can see that the MPM ecosystem, which is where modules for Node.js are published, is one of the fastest growing and has the largest number of modules. There's a great ecosystem of modules and code that you can reuse. Again, leading to great productivity for your development teams. I mentioned performance. This is one of the reasons that people are interested in Node in that it is performant in a number of the different ways that matters today, especially for cloud native deployments. It's small, very small download and even uncompressed size. It's got fast startup and small footprint. All things that you want to do, if you're going to be deploying applications and say microservice type deployments and to the cloud. It also delivers at the same time great performance in that it's an event loop-based approach can deliver things like 10,000 concurrent connections, where runtimes with a threaded-based module would have a really hard time or struggle to be able to manage that kind of scalability. At the same time, development teams have found that they get great productivity increases by moving to Node. That's one of the reasons actually that we think as a new language or a new entrant, it's gained so much popularity. People report that you get faster development with less code. There's a study from quite a few years ago that PayPal reported that they coded the same application in Node and in Java, and they ended up with taking half the time with less people and 33 percent fewer lines of code, and less code means less code to maintain. So that's one of the great things that keeps on paying you back afterwards. This is a good example here of, in four lines of code, we have a fully working web server Hello World, but it's not a lot of code. I can write this into a file, start it up under Node, and basically I'm already serving responses with very little work. Because of the attributes that I've talked about, Node.js has found use in a lot of different applications, a lot of different use cases. This is a list of use cases that the Community Benchmarking Working Group put together a while back, and you can see that it ranges from backend services, microservices, all the way down to running in embedded systems, IoT type systems, and I just added a few of my own. There's support for using Node with machine learning through things like TensorFlow.js, and you can even do integration and graphical type programming through things like Node.Ret. So really, Node has found its way into a large number of different use cases, from running scripts to running the backend services that you're relying on. I also want to make it clear that Node has its use and is used in very large applications. One of the applications that's operated by our partner IBM is weather.com. I think this is a great Node success story. It's a large application serving weather all the way across the world, so it's internationalized, it serves more than 60 languages and 230 locales. It's a large Node application deployed to Kubernetes across four regions, seven clusters, 400 worker nodes, and dozens of services all running on a Cloud infrastructure. So again, this is an example where Node is running at scale. We also see this in a lot of other companies out in the ecosystem. Now, Red Hat is involved in a number of different aspects of the Node ecosystem. One is the community, we're very much involved in helping to build the Node runtime itself. We have four people on the technical steering committee, we're involved in a good number of the working groups, and our focus is really on the enterprise requirements. So what we believe is important to our customers and people who are running those applications at scale. So working to make sure that we have stable and predictable releases. We have Bethany Griggs, who's a member and helping to lead the release team doing releases and helping to manage those schedules. We have work, so I think people like Jerish Poonatel in the diagnostics working group to help improve our diagnostics. And if you see Node report currently called, I think just diagnostic report when we pulled it into core, that's something that we helped get in, and I think it was a very good addition. We also focus on things like security and performance, as well as internationalization and the general code quality and safety net so that the releases come out with a good level of code quality. In addition to working in the community, we also work on making sure that Node runs well and is well supported in Red Hat platforms like Red Hat Enterprise Linux, where we deliver containers, both in RHEL containers and UBI containers, so that you can get and use Node.js in supported environments, as well as OpenShift, where we work to create modules like Node.Shift, which will let you very easily deploy your Node applications to an OpenShift environment. We're also working on something we're calling the reference architecture, very fairly early stage, but this is to help answer questions we get quite often around what modules, what components should we be using in our Node deployments. Now, there's lots of opinions on that, we're not trying to tell anybody what they should use, but more and more at both internally and from our customers, we get the question of like, hey, what do you think we should be using? And we're just trying to answer that in terms of what we would start with based on the experience and those large deployments like the Weather Company that I mentioned in terms of what's out there. So if you go to the Node.Shift website, you can get sort of more information about some of that, as well as to the GitHub repo, where you'll find the modules like Node.Shift that I talked about, things like Kube Probe, which is a module for health monitoring, things like Apossum, which is a module to help do circuit breaking, and other components that make up a part of that reference architecture. So I'm hoping that this is basically giving you enough insight and interest that you're now gonna wanna dive more into the resources that we have available in terms of Node and getting to know what Node is and how you can use it to solve your business problems, as well as what we're doing in the community and as well as in the Node community itself, as well as within Red Hat in terms of the Node.Shift project. And so I invite you to come and explore the resources that we're making available through this landing page, and we hope to talk to you and engage with you going forward to understand what kind of things you're looking for when you're deploying your Node applications and working towards making our platforms the best place to deploy those applications. Thank you very much, bye.