 Hey Michael. Hey, how you doing? Good. How are you? Good. Thanks for coming over. Yeah, thank you for inviting me over. The tea is delicious. Yeah, I always like to sit down and have a nice cup of tea. Yeah, it's very pleasant. I feel like we're forgetting something though. What what would that be? I mean, where else could we need to be right now? Something happening right now? Oh? Oh Is the open JS world event now? Oh geez, you're right. We're supposed to be on stage. We're doing a keynote We better get cracking on that. Okay Let's let's head over there right now Okay So I guess before we get started we should probably introduce ourselves Sure, um, I'll go first. I'm I'm Joe Seppi. I work for IBM as an open source engineer And uh, the great thing is that's a lot of the work that I do is in the community in in the Node.js project and with the OpenJS Foundation And I'm Michael Dawson IBM's community lead for Node.js That means I get to spend like Joe a lot of time working out with the community But also working with our internal teams who are, you know, building tools to Help you deploy efficiently with Node.js Teams that are deploying, you know making large-scale Node.js deployments And just, you know, supporting our customers and internal teams who are using Node.js So today Michael Yeah, who says elephants can't dance with Node.js and JavaScript Michael Well, you know, I sometimes hear that people think IBM is a big big company with like a lot of history And you know has a hard time sort of changing ship or or getting into some of the new technologies Yeah, a hard time. So what's the challenge? Um, really, you know the challenge is is that uh, you know, sometimes that perception gets in the way of people engaging and uh It's a sec. Sorry There we go. Got the challenge. So sometimes, you know, it gets that perception gets in the way of people engaging and it's really a missed opportunity because You know, IBM is doing a lot of things in the Node and JavaScript front in the community Um, you know internally and I think, you know, if people really knew all the things that we're doing that that Perception wouldn't really have stuck around for quite as long as it has I agree. I think of uh, I think of it as like a big ship, you know, it takes a little while to turn a big ship but big ships do turn And um, you know, IBM isn't great at shooting its own horn, but uh, we we really do a lot in the Node.js uh space for sure Yeah, so I think if you look at, you know, the reality of what happens is, you know, IBM is really very active in the open source communities Um, you know in the Node.js uh project the open.js foundation work in the cpc We've done a lot of work in terms of making sure that node runs on IBM platforms As I mentioned, we use node in some very large applications internally Um, we're building great places for you to deploy your Node.js applications And even working on tooling that, you know, when you're doing your initial development that will help you be more efficient Um, and help you make sure that when your application does get to production, it's it's going to be successful And then finally, we you know, we spend a lot of time Working with our customers both internal and external Um, you know, we have whole groups like the the the IBM cloud garage that are that are oriented towards helping customers Come and use new technology and solve new problems. So really, you know, we're we're involved in all those different areas Yeah, and I think I think that this isn't just Node.js as well. You know, this is a variety of open source tools IBM really builds on open source and has been involved in open source for for many years You know Node.js, but also containers We we have a lot of work that we do in that space as well Um, really deeply involved in in open source. Yeah, I know very actively involved in cncf and you know I think we were one of the earlier contributors to to even the linux foundation. So it's been a really long standing Longstanding contribution involvement and I think it's just that perception of you know A company that's been around a long time That is maybe slowing down, you know, people understand people seeing the the the the way that IBM is acting here So one of the things we meant we talked about was the open source contribution So maybe, um, you know, we should talk a little bit about the open.js foundation I know you're acting as the chair and it would be good to know a little bit more what's going on there Yeah, sure. So, um IBM's been deeply involved in the open.js foundation. We had a number of folks Play a role in the merger of the Node.js foundation and the JS foundation And we were, you know involved in both of those foundations before the merger I'm the chair of the cross-project council. We have a couple other members in the cross-project council that are IBMers Including Michael and and a couple others Uh, but in addition to that we have a number of projects that we're we're very involved in That's part of the foundation Including Node.js, of course But also Node red The the creator of Node red is uh, nickel eerie. He's he's on my team as well And also chris hiller, who is the lead maintainer for mocha is is on We're all same team So we talk pretty regularly and meet regularly to um to advance the work of the of the foundation Through the cross-project council as well as the board and I know you're on the board my coastal alternate over you Yeah, I mean really I see our involvement is like grassroots in the projects Like you said to working on the cross-project council to help with the governance and help bring new projects in But we're also involved in the board. Todd Moore has been the the chair of the board for for a while And he's been a really big supporter of Node.js as well This year. I also had the opportunity and privilege to serve as the Node.js board representative for on behalf of the Node.js project And you know, so I've been able to be involved and and and contribute at that level as well, which is great Um, you know, so overall, you know, I think the open.js foundation Is really important because it's the place where we hope people will come together to collaborate on javascript and and Node.js um And to to sort of give it give a place where people can come and do that Along those lines, like one of the things I'm excited about is, you know, I've made a proposal for collaboration spaces and the concept there is to provide a place for People to come together and collaborate under the the open.js foundation getting support with things like, you know, uh um github repos Use of our our slack channels and zooms and all those things those small things which can actually make a pretty big difference Um without having to be a project So, you know today the the foundation already supports projects, but this would let, you know, non projects You know have a people come together to collaborate on areas under the foundation that are not necessarily tied to a specific project So for example, if people have an interest on security They could come together and work on things that are important to javascript security in a collaboration space Yeah, infrastructure there are a variety of places that I think could be great collaboration spaces Yep, and and hopefully the end result is more people getting involved and and coming out to participate Yeah, so what what kind of Work are we doing within IBM sort of around some of those spaces that uh that IBM's involved in So one of the big ones is is the no j s community, of course You mentioned some other projects in the cpc, but no j s is is one where we were significantly involved And due to our, you know, a long history of working with enterprise customers our focus is often on enterprise type requirements We were involved from the very beginning in terms of Putting together the lts release process To support stable and predictable releases. We now know that we're going to get You know a new current Every april and october and that in october that you know the previous current From april is going to become an lts release. So we know that, you know, we have that predictability As well as we know that we have, you know, 30 months of support once the release goes lts Diagnostics is another one that, you know, we're very active in That's important to be able to support our customers when you're in production You want to have the best tools available Node being a little bit of a younger language still has some some work to be done on that front So that's one of the areas that, you know, we're definitely active in working in Jerice punitel is helping to lead an effort there on Putting together some best practices and you know Then taking those best practices and making sure we have good tools in the node ecosystem to support them Security is obviously one that's always important to people And you know, we've been involved in the security working group helping to define things like the security processes And helping to manage the security releases There's a lot of work just pulling together all the different pieces of the puzzle to get one of those releases out So we've been pretty active there Performance is of course important because everybody wants to get the most out of the hardware that they're buying We have some, you know As I mentioned, you know IBM has some large enterprise customers and and many times those those customers run in a number of different languages And number of different countries. So internationalization is important So that's an area that we've been involved in as well And then finally it's just important that we have good quality releases. So we we help with the code quality Um efforts things like the code coverage site other aspects of the safety net like um Sygem was originally contributed by an IBMer And just generally doing you know helping out with the infrastructure to make all that stuff good Yeah, yeah, and we have a number of collaborators in the the node.js platform as well, right? Yeah, I think it's a recognition of you know How much we contribute that we have 10 core collaborators people who can review and land commits As well as three people on the technical steering committee who you know help to Figure out the the edge cases where the collaborators can't come to an agreement on their own And it's it's great that we can be you know contributing and helping to lead on on that front And you mentioned uh releases earlier. Um, I know uh beth Manages the releases for the platform. Isn't she I believe she's going to be interviewed by the foundation for this event Yeah, we there should be like a featured article on her. So if you're interested you can you can go check that out for sure And then she has a talk I believe as well, right? Yeah, her talk She's talking about some great work that's being done in the package maintenance working group along the lines of you know helping Maintainers to be able to test not not the same as Sygem, but something along the same lines In terms of being able to test dependencies People who depend on your modules and packages. So anyway, that should be an interesting talk as well Do we have any other talks on the foundation event? I think you're giving one, aren't you? Oh, yes, I am That's true. Um, is anyone else? Yeah, we have chris heller is is giving a talk on tooling I moderated a security panel And I think there's a talk by um On node red as well Great, great. Yeah Excellent So what what are the other things, uh, you know, this is in the in the community, but also that's kind of important is um You know, we have put a fair amount of work to make sure that no gs runs on ibm's platform So anything from you know linux on z linux on p aix um or even ibmi where jesse gorzinski who does a great job advocating for open source on ibmi tells me It's like up to 25 of our customers are using node on ibmi now It's it's actually when I go to the conferences It's just great to see how excited people are about no j s in in that environment where you know, they're They're in businesses Maybe they're supporting manufacturing or some other types of factories And it's it's great to see them starting to use no j s for all that kind of work as well No j s on the mainframe and that's right and mainframe is is another area where you know people there's significant interest of people Starting to run, you know, the right workloads to get the advantages that you do with node Yeah, we have a lot of internal use of node j s as well. Um multiple teams multiple projects A variety of ways where we're implementing node internally Um and a very vibrant community through slack channels An assortment of them. I think the node j s channel has 1600 people or more And some some major deployments as well, right michael Yeah, oh, definitely and on that major deployment front There were a couple that we wanted to share today just to show you the scope of some of the deployments that we have in In ibm the first one is the ibm cloud console. So if you've ever gone to use The ibm cloud it provides the ui Um, and this lets, you know, you create those different services like whether you're creating your kubernetes clusters Uh virtual servers bare metal machines cloud foundry type applications server serverless applications the cloud ui is is a node j s application supporting all of that It also provides sort of a plug-in framework In that when we want to bring a new service because the ibm cloud provides services in addition to those sort of foundational components like open shift and kubernetes We have teams who want to deliver services through the cloud and it provides a plug-in type architecture where They can easily take advantage of things like registration onboarding access management billing usage Without having to rewrite that all and it's all written in node j s, which is great Yeah, that plug-in that plug-in approach is really smart. It allows a lot of uh teams To to to take advantage of the platform Yeah, and and you know as we can see there's over 50 teams who've taken advantage of that So that just gives you an idea of how much use there is and that we have 50 different teams who've just contributed Uh, you know node j s applications to the ibm cloud The the application itself is over 90 microservices. It's deployed to kubernetes And it's distributed over 10 different You know geographically load balance clusters across the world. So really a big node application that we run 24 7 Yeah, the ibm cloud console is a great example. I think the weather company is another one, right? Yeah, the weather company is the next one in that You may have even gone there to check your weather. You can get the seven day forecast You can also, you know, it has a whole bunch of api so it can help you make your application better by incorporating weather data And in a lot of cases, you know, that can really add value. For example, if you've got You know a site that helps people pick when they want to plant seeds or anything else related to growing Food or or plants It'd be great to be able to give them insight in terms You know, maybe when it's going to be a good time to do things based on the weather or not Yeah, I was a part of a Proof of concept application that we built that was a logistics company and we used weather apis to Know when a storm was happening or going to happen and reroute Shipping routes to accommodate for these sorts of storms and such. Yeah, that stuff's really really really important Yeah Looking back to the application itself again, it's another big node js application It's it serves billions of locations, you know, all sorts of cities zip codes Internationalized we mentioned internationalization before 60 languages 230 different locales And it's deployed in four different regions Seven kubernetes clusters 400 more than 400 worker nodes Dozen services, which can be like maybe three replicas or 100 replicas Again all running on the ibm cloud 247 So, you know another really big node js application that you know ibm runs and operates You know just showing that what you can do with node js and and how we're using Yeah, let's let's take a moment and talk about Deploying node js on ibm cloud Right. We we just wanted to mention a couple of ways you can deploy node js Um You know one is the ibm public cloud and the other one is ibm cloud pack for applications If you don't necessarily want to move all of your workload up up to the cloud In terms of the ibm cloud You know, it it's it provides a whole bunch of services Sort of foundational services. So things like Open shift kubernetes serverless You know, but in addition to that it loads in a whole bunch of services So if you need a database you can get a service for that if you need to connect to iot devices There'll be a service for that if you need to send emails, there'll be a service for that So it it's broadly, you know has the data centers all over the world And really provides you all the components that you'll need to deploy your node js application successfully and scale as you need to across the world Yeah, I'm using the ibm cloud pack for applications. It's a great way to do that Yeah, it's it's You know, if you don't want to move all your applications up to the cloud The way I look at ibm cloud pack for applications is there's lots of great Projects in open source and I could go and collect all those together myself But it's a little bit like building the car by yourself. Do you want to go out? Buy all the parts source all the parts put it together That's probably going to take you a lot of time and effort just to get to that point And once you've done that you're you're probably on your own for support because you've built your own custom the spoke You know infrastructure ibm cloud pack for applications builds on those tried and tested open source applications, but brings them all together into a nicely packaged You know offering so includes open shift things like tecton Runtimes and packages them all together as an integrated piece you can buy and then get support for so if you don't want to move all your your Applications up to the public cloud ibm cloud pack for applications is a great option for you know Having a cloud like infrastructure being able to deploy cloud native applications in your own environment Or some mix where it's it's a hybrid, you know, some things locally and some things up in the cloud as well And you you mentioned support as well, right? Yeah, so, you know once you get your application to production. It's of course important To many people to be able to have a trusted partner that can that can help you out Not everybody has enough has as much time And resources to be able to be involved in the no gs community. So be able to like, you know, if you find a bug Contribute a pr get it reviewed get it landed and that's something that you know IBM can do for our customers because of our involvement there We have we have a number of different options because you know depending whether you're running in the ibm cloud You're running on red hat enterprise linux, uh, you know through our red hat partnership Or you're you know deploying on your own in the main frame You're going to need different types of support So we have a number of different support offerings and you can find out more information about those at that link And speaking of finding out more information To learn more about all the stuff that we've been talking about you can go to developer dot ibm.com Slash technology slash node j s It's right on the home page of the developer dot ibm.com site as well And uh, there are a number of articles and tutorials and deployment options and All the things that we've been talking about are available there as well Yeah, there's a whole bunch of great content if you're interested what uh, you know any of those A number of our collaborators are doing we have a video series of talks, you know one on one with the people about what they're doing in the community And you know a wealth of of of articles on things like security And how to do deployments and and that kind of stuff so I was going to say the the weather company Architecture and deployment is uh highlighted there as well as on the open js one. Yeah, no, that's definitely a great article So thanks for everybody for watching. I think unfortunately our time time is up and thanks joe for sharing some tea with me Yeah, i'm glad that we remember this was happening because uh, that would have been embarrassing Yeah, I know I I'd hate to miss that but uh, anyway, thanks everybody and hopefully we'll see you all virtually at the rest of the conference Yeah, enjoy the event