Under the high patronage of his majesty the King Mohammed VI
Devoxx Morocco 2023 🇲🇦 October 10-12, Taghazout Agadir, Morocco.
Follow Us On
Under the high patronage of his majesty the King Mohammed VI
Devoxx Morocco 2023 🇲🇦 October 10-12, Taghazout Agadir, Morocco.

Speaker details

Antoine Sabot-Durand

Antoine is a Java Champion and the Former Jakarta EE CDI spec lead. He was part of the Quarkus launch team at Red Hat and worked on major MicroProfile specs such as Fault Tolerance or Health Check. Today, Antoine is architect and technical expert in SCIAM. He is working on challenging projects with most of the technology he contributed t in the past.

When he doesn’t code or design applications, Antoine likes to spend time with family and friends playing boardgames or traveling.

As cloud-native architecture is getting more and more momentum, the need for cloud ready implementation of popular java business solution is increasing. Business Process Management (BPM) is following this historical evolution.

When it comes to create BPM workflow in Java, jBPM and Drools engines are the first solutions that comes to most developer’s mind. They are open source, easy to set up and very featured. However, they were not built for the cloud.

Don’t despair! Kogito is here to solve this limitation

Kogito is an open-source project by Red Hat. Its goal is to bring the Red Hat business automation suite to cloud.

This talk will start with a short introduction to the main BPM concept, especially on the Business Process Management Notation (BMPN), that allows business analyst to graphically design their workflow.

Then, we will show, in live coding, how to create a pure cloud-native workflow with Quarkus and Kogito and deploy it to OpenShift (or Kubernetes).

The result will be a REST microservice able to orchestrate other services.

You’ll leave the session with the code produced and the urge to test this nice piece of technology in your own project.

This session will be delivered in French.


Our industry is rather amnesic. Today, most young Java developers ignore what happened during the early 2000’s that led us with the frameworks and tools we are using today.

That’s too bad because this knowledge would help them to be better developers by understanding the long and winding road, we went thru during these last 20 years.

In this session I’ll go back on the major events of this story with a trolling level at the minimum possible.

We will travel in time to understand the EJB curse and see the Spring 1.0 birth. Then we’ll explain EJB 3.0 reinvention, CDI emergence and Spring Boot launch.

The temporary end of the story will lead us to talk about MicroProfile, Quarkus and Spring Native. 

During our journey we’ll try to understand the naming malediction that turned J2EE in Java EE and then Jakarta EE (and no, JEE doesn’t exists). We’ll also try to explore most Spring attempt to build a profitable business model.

At the end of this talk you should have a better overview of the Java Enterprise ecosystem and understand why you should remove J2EE or Java EE (and of course JEE) from your CV if you only are a Spring expert.

This session will be delivered in French.