jakarta ee

 The aim of this talk is to answer the following questions:

• What is GraphQL?
• How does it compare to REST: competitor or complement?
• How does it fit with Java in general and MicroProfile in particular?
• What is MicroProfile GraphQL?
• Why should you care?

Going from an introduction to GraphQL, a presentation of MicroProfile, a live demo, we want the audience to get a better graps of what MicroProfile GraphQL can provide to develop modern APIs.

We live in an era of building enterprise software with build pipelines, containerization and clouds in order to provide business value. In order to maintain the quality of your software and fast delivery, you must optimize the development process and release strategy with tools and concepts that complement each other.

This session will teach the attendees on how to achieve this by using the Jakarta EE platform with the addition of Eclipse MicroProfile, that are a fit for scalable environments like clouds. The attendees should have a basic understanding of the concept of enterprise development with Java EE / Jakarta EE and/or Spring Framework.

We live in an era of building enterprise software with build pipelines, containerization and clouds in order to provide business value. In order to maintain the quality of your software and fast delivery, you must optimize the development process and release strategy with tools and concepts that complement each other.

I will provide insights on how to achieve this by using the Jakarta EE platform with the addition of Eclipse MicroProfile. The audience should have a basic understanding of the concept of enterprise development with Java EE / Jakarta EE and/or Spring Framework. They will learn how to develop Jakarta EE and MicroProfile applications that are a fit for scalable environments like clouds.

To develop a cloud ready application is only one side of a medal, the other side is the cloud environment hosting this application. As a software architect you have to make some decisions giving a consideration to your target runtime environment. Some aspects like configuration, fault tolerance, health checks, application metrics, request tracing and service discovery have a strong coupling with the cloud environment. Eclipse MicroProfile has a lot of specifications to make your Jakarta EE based application ready for the cloud.

The Jakarta EE Community is still finding it's wings. But, that's not stopping the JAX-RS team. This team was the first Jakarta EE component out of the chute and ready to make waves. They tested some of the boundaries before the boundaries even existed. This session will introduce you to the Jakarta EE community and processes in general.  And, you will have the opportunity to learn from one of the JAX-RS leads and their experiences.

MicroProfile is well established as a microservices development platform. It blazed the trail for the Jakarta EE movement. In it's short tenure, MicroProfile has introduced us to the Fault Tolerance, JWT Propagation, Metrics, Rest Client, Config, Health Check, OpenAPI, and OpenTracing programming models. But, what's next for these two key Eclipse projects? Will MicroProfile stay independent and continue to demonstrate it's fast-paced innovation? Or, will it be combined with Jakarta EE, which is also promising a faster development cycle than the previous Java EE platform?

Already we can see and feel that the development of "Java EE" after the contribution to Eclipse will be different from the past.  We are seeing enthusiasm and participation from the various teams at an all-time high!  But, what will be different after these contributions to EE4J (Eclipse Enterprise for Java) is complete?  Come to this session to learn what's changing, besides just the name...  :-)  I will give you an overview of the projects already transferred and what projects are left.  I will also give an overview of the new and updated processes, as well as what processes still need so

During 20 years, we have been accustomed to Java EE (previously J2EE) managed by the Java Community Process. Not all of us were fully happy with this situation: we have often been frustrated by its slow process and its sometimes bloated specifications. But at least,  it was considered as a long-term standard.  In less than 6 months, everything has changed and now, we have Jakarta EE managed by the Eclipse Foundation. Who could have imagined such a change in a short period of time?