Book Image

Cloud-Native Development and Migration to Jakarta EE

By : Ron Veen, David Vlijmincx
Book Image

Cloud-Native Development and Migration to Jakarta EE

By: Ron Veen, David Vlijmincx

Overview of this book

Cloud-Native Development and Migration to Jakarta EE will help you unlock the secrets of Jakarta EE's evolution as you explore the migration and modernization of your applications. You’ll discover how to make your code compatible with the latest Jakarta EE version and how to leverage its modern features effectively. First, you’ll navigate the realm of cloud-native development as you demystify containers and get introduced to the Eclipse MicroProfile, a powerful tool in your toolkit. Next, you’ll take the bold step of transitioning your applications from local hardware to the limitless possibilities of the cloud. By following the author’s expert guidance to deploy your Jakarta EE applications on Microsoft Azure, you’ll gain hands-on experience in managing cloud resources. In the final leg of your journey, you’ll explore the world of serverless architecture. You’ll learn to design and run services that are truly serverless, harnessing the potential of the event-driven paradigm for scalability and cost-efficiency. By the end of this book, you’ll have mastered Jakarta EE and become a proficient cloud-native developer. Join us on this exciting journey of transformation and innovation as you pave the way for the future of Jakarta EE and cloud-native development.
Table of Contents (18 chapters)
1
Part 1: History of Java EE and Jakarta EE
4
Part 2: Modern Jakarta EE
8
Part 3: Embracing the Cloud
Appendix A: Java EE to Jakarta EE names
Appendix B: As a Service

MicroProfile Config

According to the 12-factor app document drawn up by the people at Heroku, an externalized application configuration is an essential part of being cloud-native. Think of a URL and the credentials to a database. In container environments, this is mostly achieved by setting environment variables.

MicroProfile Config is meant for this and supports a lot more configuration options than just environment variables.

It supports a hierarchy of locations to look for configuration values. Each of these locations has an ordinal value, and higher-valued locations take precedence over lower-valued ones.

These locations are called ConfigSources. Three ConfigSources are required by the standard:

  • A property file, META-INF/microprofile-config.properties (100)
  • Environment variables (300)
  • System properties (400)

The number between brackets is the ordinal value, so system properties have the highest priority. Accessing these system properties in your...