Book Image

Jakarta EE Application Development - Second Edition

By : David R. Heffelfinger
Book Image

Jakarta EE Application Development - Second Edition

By: David R. Heffelfinger

Overview of this book

Jakarta EE stands as a robust standard with multiple implementations, presenting developers with a versatile toolkit for building enterprise applications. However, despite the advantages of enterprise application development, vendor lock-in remains a concern for many developers, limiting flexibility and interoperability across diverse environments. This Jakarta EE application development guide addresses the challenge of vendor lock-in by offering comprehensive coverage of the major Jakarta EE APIs and goes beyond the basics to help you develop applications deployable on any Jakarta EE compliant runtime. This book introduces you to JSON Processing and JSON Binding and shows you how the Model API and the Streaming API are used to process JSON data. You’ll then explore additional Jakarta EE APIs, such as WebSocket and Messaging, for loosely coupled, asynchronous communication and discover ways to secure applications with the Jakarta EE Security API. Finally, you'll learn about Jakarta RESTful web service development and techniques to develop cloud-ready microservices in Jakarta EE. By the end of this book, you'll have developed the skills to craft secure, scalable, and cloud-native microservices that solve modern enterprise challenges.
Table of Contents (18 chapters)
15
Chapter 15: Putting it All Together

Developing microservices using Jakarta EE

Now that we have briefly introduced you to microservices, we are ready to show an example of a microservices application written using Jakarta EE. Our example application should be very familiar to most Jakarta EE developers. It is a simple CRUD (Create, Read, Update, Delete) application developed as a series of microservices. The application will follow the familiar MVC design pattern, with the “View” and “Controller” developed as microservices. The application will also utilize the very common Data Access Object (DAO) pattern, with our DAO developed as a microservice as well.

DAO Pattern

The DAO design pattern is one that allows us to separate data access code from the rest of our application. Allowing us to switch the implementation of the data access code without impacting the rest of the application code.

Our application will be developed as three modules – first, a microservices client, followed...