 All right. Well, thank you Hello, everyone and welcome to the reactive summit 2022. It's great to be back out live in the world again as She said I'm Hugh McKee, I'm a developer advocate at light band and code co-chair of the reactive summit and We're delighted to have you here today. We've we've got a great incredible lineup for you planned for today there's some great talks and I think we're gonna have a range of some people Probably been in the reactive space for a while, but some people might be newcomers but it's all it's all a an opportunity for you guys to learn and take some things away and Also, you know connect up with the other people. This is one of the great things about being back out in live conferences again Before we get started, I'd like to thank our sponsors, especially light band the platinum sponsors light band and yop works and Just a few housekeeping reminders Please remember That we have an event code at the conference that everyone has agreed to and will be enforcing and short basically, it's everyone should feel welcome and included and Please treat everyone with respect and professionalism any concerns go to the the Registration desk and the the event team will help you out and Finally The conferences asked that we wear masks while we're not talking and not and when you're not eating or drinking so Just the massacre required at the conference So before I introduce the first speaker the keynote speaker. I wanted to just spend a few minutes talking about reactive and a little bit about what it means to me, but I think a lot about what it means to you and React has been kind of interesting, you know, Jonas Spinner who's one of our keynote speakers will be talking a little bit but Jonas and some others put together what was called the reactive manifesto back around 2013 and In the reactive manifesto it really focused on What we now kind of clarify as reactive systems But in the years since then Reactive really kind of took off but it took off in the reactive programming space Which was great because it was a new style of programming. There was much more efficient use of system resources You know infrastructure resources things like that, but in my heart and what attracted me I've been with Leipan for about six years now and before I came to Leipan. I was an enterprise IT That he'll the Packard and the bane of my existence. I was a developer and architect but we had these things when we had production outages we called them escalations and You know these systems ran 24-7 and of course the odds are that the system is going to go down when you're not working like on a weekend and So this is a selfish motivation Why I really kind of became interested in reactive systems because in a way it was like I was on these You know like marathon calls. I think many of you been here, right? You have a production system. It goes down It's on a weekend You got to get on the phone You got to leave your family. So your family is not happy with you Your management is not happy with you. Your customers are not happy with you So there's this incredible pressure to get the system back on and you can be on these calls for hours You know like overnight type of thing trying to resurrect and get the system back online And I'd be on these calls as like I'm vowing. I never want you never I'd never want to let this happen again How can I do this? How can I get out of this situation? So when I saw the reactive manifesto, I think I saw it around 2014 time frame It's like okay. These guys are kind of speaking my language and with the reactive systems, it's there's really kind of four Aspects of it that are the key to it and they're kind of pretty intuitive It initially kind of obvious, but there's a lot of depth to my thing So the first one is you want to build a system that's always responsive. So it's easy to say But it's not easy to do But by always responsive it means the users always, you know, every time they want to use the system It's it's a 24 hours, you know, 24 seven system. It's available to But the in order to do that There's kind of two key other characteristics of a reactive system One is that the system is always responsive under load So the system can scale so it can scale up when the load goes up and the system Can scale down which is nice a nice feature if you can scale up you can scale down So the nice thing about being able to scale up, of course, you can handle the spikes and traffic You can scale down you can save money which could be big money Just real quick at HP. We had like I think there were like 50,000 servers This was around the 2010 20, you know early 2010s and The overall utilization of the servers were on 10% Throw the IT management nuts You know the all this lovely hardware and we're using a 10% of it because they were over provisioned to handle the spikes So you can scale down you can save a ton of money But the more interesting other characteristic of reactive system is the system's responsive when things fail And that's the fun part. I think that's the real challenge How do you build systems that are going to keep running when things break? and This is where the fourth and final characteristic of a reactive system comes in which is messaging and really if when you read the Manifesto it talks about asynchronous messaging but really what's going on there is it's enabling loose coupling of components and this is a key ingredient of resiliency if you can build a system where component a is not dependent on component B Because when component B goes down to component a doesn't care then you're in a good place, right? Your system is more resilient. So this whole loose coupling which we talked about a lot with microservices For example, this is the strategy and the motivation But the the guilty motivation is that I don't want to get those phone calls In the middle of the night on the weekend when I'm with my family And I don't want to be on those high-pressure calls anymore that the most wonderful thing is when you build a system and you Something crashes and the system keeps running Of course, it has to be fixed, but we're not down. That's a beautiful place to be I remember the first time we showed our management and Aka system where we could kill nodes and the Application kept running. They were like they would sit there almost like little kids in Glee. Oh, that's so wonderful They want to go and brag to their other managers. They look my applications can have pieces go down and it still runs That's where you want to be. This is what reactive is about. So I think it's gonna be interesting as you go through the talks today It'll be all over the map in terms of where things fall on the spectrum of reactive reactive programming reactive systems, but A lot of it's motivated by these these fundamental characteristics and it's it's a deep and fascinating area And I really hope you enjoy the the conference So with that I want to introduce our first keynote speaker Mary Grigelski Mary is a Java champion and a passionate streaming developer advocate at data stacks Mary and I run into each other at conferences all over the place She's amazing though because she transitioned from a UNXC programmer in 2000 to Java. I never look back she's Considered a self-apoligot loves to continue learning, but I think the big thing Mary is a force especially in the Chicago area with promoting conferences and Getting things going and and and you would became a Java Java champion last year, right? So we're very delighted to have Mary be with us this morning. Welcome Mary