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

What is container orchestration?

In Chapter 6, you were introduced to Docker. You learned that Docker is a way of building and packaging software, allowing for easier distribution and execution. You also learned in the chapter about Jakarta EE and that it has introduced a specialized profile, the Core Profile, targeted at microservices and containerization. You are likely to have many containers running, and this is where container orchestration comes into play.

Container orchestration is the process of creating, scheduling, scaling, and monitoring containers. The number of containers that are required to run an application can quickly grow, even a standard architecture with a frontend, backend, and database – that is already three containers. And then you have additional requirements, such as a caching instance, a reversed proxy, and a CDN (https://en.wikipedia.org/wiki/Content_delivery_network) server.

Also, you might want to have more than one instance of each, in case...