 This is Jason Porter with the Red Hat Developers Program. I'm here with Clement Escoffier. Oh, very well. And you work on the Vertex project, correct? Yes. Very good. Very good. Now, Vertex is one of the technologies, one of the projects that we have that's actually, frankly, quite different from most of the other things that we have in middleware. So could you give just a quick overview on what it is and why I would use it? So Vertex is a toolkit to build reactive and distributed system. It's made for application where you have a high need of scalability and where you really want to embrace the asynchronous aspect of the computer system to efficiently use your resources. So it's a bit different from all the portfolio we have because it's really embracing asynchronous and to end. So your code is going to be asynchronous. It's a bit from an enterprise developer point of view. It's very different because you have to handle and embrace this asynchronous aspect, which can be very confusing at the beginning. But it's where Vertex can give you a lot of freedom because you can pick the way to handle those asynchronous aspects. For example, by default, we'll use callbacks. But yeah, while callbacks, as soon as you have a lot of callbacks, it starts to be not really readable. Then we can provide reactive programming. We have a very neat integration with Erics, reactive extension. And you actually know of asynchronous application in a very elegant way. And Vertex is polyglot. You don't like Java? No problem. We have Ruby, Salon, Scala, Kotlin, JavaScript, Groovy. And yeah, I don't know the list. But yeah, we have a couple of languages. It's a large list. Yes. Very good. So yeah. So what about Vertex is the most interesting thing for developers? If you really want to look at a different pattern, if you want to do code differently, if you want to really focus on performance and stop lying to you by thinking that the network is synchronous because it's not, then use Vertex. You may find it very different at the beginning. But once you start using it, you will see that you will become way more productive than with a regular stack. We have lots of tools. You have a lot of freedoms. You can really decide which language, which way to build your application. We have lots of modules. We have Vertex Web to build modern web app. We do IoT too. We do integration with Apache Camel. So we really have a big ecosystem. And the beauty of Vertex is that this ecosystem, we do a part of it. But the community is providing really, really lots of new modules. And it's a very thrilling community. It's really great to be involved in such kind of project. Oh, very good. Vertex also plays a little bit in the microservices space, doesn't it? Yeah, definitely. Because microservice applications are inherently distributed. So using asynchronous and asynchronous development model, asynchronous architecture, reactive architecture, make a lot of sense there. So when I speak about reactive architecture, that means systems that will stay responsive, even if there is a lot of users, so pick off loads, or if there is failures. So your system is still there for you. And to do that, you need to really embrace asynchronous. You need to build your system with this in mind. And Vertex enables this for you. And you will see it's really natural to build microservices without. Speaking about this, I just released a book using Vertex to build reactive microservices. It's available here. Is that the title of the book? It's Reactive Microservices with Java. OK, all right. Very good. Very good. And I believe that's also being showcased on the developers.redhat.com. Yes, yes, definitely, yes. Very good. Now, just to get started with Vertex, where do I go to find more information? HTTP.vertex.io, that's our website. You have all the documentation in all the language that I have just cited. So you have everything, all modules that are supported. We have got code examples on there. Oh, yes, a lot. We have a blog, which we have a blog post series called Introduction to Vertex that tells you how to build a CRUD-based application or database works in a reactive world, because database are blocking. So how does that work? So there is this. We have an Android Labs. You can find the URL on the website, too, which is pretty long. It's around six hours, but it's all about microservices and asynchronous microservices and all the different way you can use to build that. And we are going to revamp this lab to use GRPC, HTTP.2 in the next few weeks. So if you are interested by these new technologies, wait a couple of weeks, and you will be there. All right, very good. All righty. Thank you so much. Thank you very much. Thank you.