Lifting and shifting existing applications to the Cloud is a common task for many deveopers these days. This session will explain 3 common scenarios for moving Java EE standards based applications to Azure using concepts applicable to other cloud environments as well. One is of course using Containers and Kubernetes; Second is by using a platform runtime such as Azure AppService. And the third is by using Service Fabric. In the end, we will see the differences, pros/cons, and also open for Q&A.
The world is moving from a model where data sits at rest, waiting for people to make requests of it, to where data is constantly moving, streams of data flow to and from devices with or without human interaction. Decisions need to be made based on these streams of data in real time, models need to be updated, intelligence needs to be learned. And our old fashioned approach of CRUD REST APIs serving CRUD database calls just doesn't cut it, it's trying to fit a square peg into a round hole. It's time we moved to a stream centric view of the world.
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?
When the Eclipse Microprofile initiative was started in 2016, it only took about three months before version 1.0 was launched. From day one, there were four different implementations from four different vendors available.
And the progress does not stop there! Whereas version 1.0 was a subset of Java EE specifications, the following versions bring additional technologies useful for building microservices.
Current version contains APIs and implementations for:
There used to be only one game in town for application servers -- You were either Java EE compliant or you weren't. And, to claim Java EE compliance, a special license was required that allowed you access to the test suites that would prove compliance. Some vendors and open-source projects obtained this license, while others did not. In short, it was not a level playing field. But, all of that is changing now that the Java EE test suites are being contributed to Eclipse under the EE4J project (Jakarta EE). All of these tests will now be freely available under the Eclipse Public License
Last fall at EclipseCon Europe we held a panel discussion on EE4J, the new top-level project at Eclipse for housing the Java EE contributions coming from Oracle. It was very well attended and had excellent discussion. Now that we are a few months further into this process, let's have another panel discussion on where we are at with Jakarta EE. We can start with some preliminary charts to explain the current state of affairs, and then open it up for questions. The make-up of the panel will be determined by who shows up from all of the Jakarta EE participants, but at least we can count on
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