Conventional wisdom has it that Java EE is a bad starting point for building cloud-native Java applications, but despite this most cloud-native frameworks are designed to use and extend Java EE. The issue has been not that Java EE can't be used, but deploying applications to new cloud platforms like Docker and Kubernetes so they can be efficiently updated and scaled requires new API's. Enter the Eclipse MicroProfile initiative which, combined with Jakarta EE, has been rapidly building out these gaps.
Ever wondered what makes a cloud-native application "cloud-native"? Ever wondered what the unique challenges are and how best to address them on fully-open Java technologies? In this workshop, you'll learn what it means to be cloud-native and how that impacts application development. You'll learn about Eclipse MicroProfile, an industry collaboration defining technologies for the development and management of cloud-native microservices.
Containers, Kubernetes, Cloud Native, Microservices, Eclipse MicroProfile. It feels like you’re going to drown amongst the buzzwords! In this session we will guide the developer through the minefield of all these buzzwords to understand the concepts and develop solutions with them.
What if there was a way you could take advantage of the latest microservice architectures by leveraging the developers and skills you already have?!? In this session we’ll show you how with Eclipse MicroProfile and Red Hat’s implementation Thorntail. We discuss all the cool features it allows you to easily use, such as OpenTracing, Metrics, and layout the current roadmap plans. Then we move onto a demo that showcases what’s possible with Eclipse MicroProfile, utilizing the existing specifications, built with Thorntail.
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.
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?