 This is Jason Porter with the Red Hat Developers Program, and I'm here with Thomas Kvostrom. Kvostrom, yes. Something like that, very good. And you work on the marketing side for EAP, correct? Yes. Very good. Very good. Now, EAP, for those that don't know, that is our product version for the application server in the Java middleware space. Yes. And what's the most current version of EAP? So EAP is currently running 7.0, 7.0 version. We are planning on releasing 7.1 somewhere during the summer, or during June probably, it's the plan right now. Very good. And that's based on WildFlight version 10, correct? Yes. And that is running the Java Enterprise Edition version 7 as well. Yes. Very good. So just getting into the support side as a product, how long do we support versions of EAP? So we support them up to 7 years, but you can also, if you actually want to have more extended support, you can have support up to 30 years with EAP, but that's going to cost a bit extra, but that's how long we can actually support EAP. So it's definitely one of our longest supported middleware products at Red Hat. Great. Very good. So the things that, you know, I get questions a lot from people in the community. If I've got WildFlight out there and EAP, why should I choose EAP? What's so different about it? Yeah, absolutely. So number one reason we shouldn't be too much differences because we are based on the same code base and the same everything, but the difference is how we consume it. So when a customer consumes EAP, they can be sure that they can run the same version for up to 13 years. Whether it be patches and updated, they will be feature-wise, they will be working exactly as the previous version. So you shouldn't experience any changes in the features and everything like that. If you're on community version, community version has a shorter lifespan. So we are patching the latest version of a community version for a certain amount of time, but after that, we move along to the next major version. And obviously that should be like that because of the speed of innovation and everything we wanted to have in the community. So the difference is actually that EAP picks up. So you can be more safe to have the latest patches and everything like that if you're using the EAP, but community is adopting new features faster. Right. Another key thing is the support channel that you have access to when you use the product and you get the support subscription. Obviously, yes. Right. If I'm using WildFlight, something breaks. The best I've got is Forms or Stack Overflow or whatnot. With EAP, I've got a support person I can contact. Absolutely. And I've got whatever my SLA is with Red Hat and I can go and talk to them. Exactly. And we will help you find issues, even if it's outside EAP, typically, so even if you have issues with other software that you're talking to or anything, we will help you. So we have partnership, for example, with other database vendors, etc. So we can actually take support tickets and carry them on to, for example, Oracle if there's an Oracle database issue or things like that. So yeah, there's definitely support is our main feature. The main feature of having an enterprise called like this. Very good. Now, for you, what do you find most rewarding working with EAP? I'm a Java guy since a long time ago. I've been working with Java E for over 15 years. So working with EAP, it feels like the EAP today is the absolute, it is the biggest open source Java E product out there. It's out of the three major vendors today. I'm not going to say which today here, but out of the three, I would say we are all the best products. One's over there, one's over there. I would say we are the leanest and best and the most performant one actually. So I really enjoy working with all the professional people in the team as well. We have really, really smart engineers in the team. It's a product that is very, very good supported. We have very, very good, actually from that perspective, it's absolutely one of our best and most stable product. It is for the middle part, it's like rail. It's a rock solid product with rock solid engineers, rock solid support, et cetera. So that's what I like to work with EAP. Very good. You said you came from an engineering background. Do you get the chance to sit down and hack sometimes? Yeah, absolutely. I'm a technical marketing person. I should say that as well. So part of my work is to do conferences like this and actually do demos and show what's happening. So for example, here at Red Hat Summit, we did a lab here where we modernized and Java applications. So we took a monolithic Java E application, put it into OpenShift. Together with OpenShift, we could also implement things like pipelines and how to deliver that, et cetera. So that was all based on being able to EAP, moving a traditional Java application into OpenShift. And then we started strangling that application and moving it over to things like while it's warm. Okay, cool. So that's one of the labs we've done, of course. So that involves a lot of coding. Oh, definitely. Definitely. Now for those out there that want to get started with EAP, where do I go? So the best way to go is to developers.red.com and you sign up for a $0 subscription. If you download the latest version of EAP, it will not necessarily have the latest patches as a developer, but you don't really care about the patches. It's not meant to be in production environment. It's the same feature-wise, it's exactly the same software that you will put in production later on. So you're free to use it for development as much as you want. Yeah, for development. That's the key. If you're looking at the $0 subscription, that's for development. And as soon as you're ready to go to production, then contact us and we'll get you signed up for a support contract. Very good. All right. Thanks for being with us today. Thank you. Have a great day.