 My name is Dimitris Andriadis I've been working on EAP in every possible capacity for the last 15 years and Now I'm herding open source developers. So I'm the engineering manager of the EP team and the wildfire community project EAP is a Java EAP application server and As such it can be used to solve a wide spectrum of problems and customers can use it from anything from financial applications, you know shopping carts Integration use cases and so on so forth. It's it's very flexible. So you can adapt it to your own use case I think the most important bit that you get with EAP is You get a very good and manageable runtime that implements a comprehensive set of APIs From which you pick and choose and use whatever you want without much of the runtime overhead EAP is important for developers because it provides you with a generic runtime Which is fully manageable and it gives you a comprehensive set of APIs from which we can Choose what you want to use and it's guaranteed to work. It's tested extensively By us and our QE. So You have a very solid infrastructure to start with. I Think what developers mostly like about EAP is its speed So it starts very fast two three seconds on developer laptop And it's not sitting so when it when we start we actually do start about two-thirds of the services We don't do lazy loading We do for some services so You you feel the speed in Your day-to-day work, you know, you can redeploy very quickly. You can start you can stop. So it's it's very nice EAP is really the Swiss Army knife of application service, which means It can be as big or as small as you want. So for example, if you run standalone or On bare metal you can have EAP as one instance or you can have a domain with, you know, hundreds of EAP instances managed by you Or you can deploy natively in the clouds Reduce EAP to the subset that you just use or just leave it like this and EAP will, you know We'll still run fast and we will consume Very few resources, you know, we can run EAP with just two open ports. It's very flexible So we can cover a wide spectrum of use cases inside or outside the clouds People associate the EAP with Java EE. I know that's very true. We are one of the best implementations out there But Due to the flexibility of the implementation You can deploy this in many different ways. You can do it micro services with the EAP Either with the whole server or with the cut-down version of the server and you still get the guarantee that The the total the sum of the components will work as you'd expect and Will be patched and will be secure which it's not something you get easily from any other customized environment one common plot problem of Developers is scale how you can scale your application, you know higher numbers high clients Transactions through put so in EAP 7 we have a our new Web server embedded in EAP. It's a new project called well new three years now project called undertow Which is designed to be asynchronous at its core meaning we can really scale up to Thousands of connection without problem. So then you have the ability to implement some reactive Pattern and solve, you know the problem having you know thousands of clients. So that's a very common scenario we can solve now With the AP 7 and undertow at its core as the web server We can now handle in orders of magnitude more connections coming into the server without any performance implications And we can also do the reverse thing you can deploy EAP as a reverse proxy so you can replace essentially Apache HDPD and have a fully manageable environment load balancers and bugging servers in EP 7 we've also changed the the messaging provider in EP 6 we had Hornet queue and Red Hat had now to let's say competing messaging implementations Hornet queue and An active MQ so the two projects have been merged under the auspices of Apache and we now have the Apache active MQ Artemis Variation which is the new messaging provider in EP which combines the good elements of Hornet queue with the myriads of connectors of active MQ One of the new features in EP 7 is the graceful shutdown capability, which is particularly interesting in Cloud environments because in you know in the cloud you can scale up but you can also scale down and Often scaling down is a much harder problem to solve. So you have to more or less Stop accepting new requests and let the in-flight transactions complete before You know getting to a halt One of the cool features of EP 7 is the new offline modes in this mode you can Start the server Essentially embedded inside the command line interface the CLI and you can configure the server without any services running or ports being Open and persist down to disk this configuration and with that you can create configurations to double for containerized environment Another cool feature in EP 7 is the BATS functionality which is defined by the EE7 spec so we were part of the Specification group and we came up with our own implementation called J. Beret And it gives you a very nice ability to do BATS style processing Much like the things you would typically do with mainframes You know if you want to migrate your old applications What's really pronounced in EP 7? It's the compatibility guarantees relative to the old version. So for example You can load an EP 6 configuration in EP 7 Their facilities to let you migrate this configuration to the new server you can Let EP 7 manage the EP 6 servers And you can have calls between the different versions and this is going to work, which is pretty cool EP is free to be used for development purposes So you can just go on a website and download it and play with it and see if it works for you I truly think it's an excellent piece of technology