You're reading from Jakarta EE Application Development Build enterprise applications with Jakarta CDI, RESTful web services, JSON Binding, persistence, and security

Product type Paperback

Published in Feb 2024

Publisher Packt

ISBN-13 9781835085264

Length 316 pages

Edition 2nd Edition

Languages

Java

Tools

Jakarta EE

Concepts

Application Development

Author (1):

David R. Heffelfinger

View More author details

Table of Contents (18) Chapters

Preface

1. Chapter 1: Introduction to Jakarta EE FREE CHAPTER

2. Chapter 2: Contexts and Dependency Injection

3. Chapter 3: Jakarta RESTful Web Services

4. Chapter 4: JSON Processing and JSON Binding

5. Chapter 5: Microservices Development with Jakarta EE

6. Chapter 6: Jakarta Faces

7. Chapter 7: Additional Jakarta Faces Features

8. Chapter 8: Object Relational Mapping with Jakarta Persistence

9. Chapter 9: WebSockets

10. Chapter 10: Securing Jakarta EE Applications

11. Chapter 11: Servlet Development and Deployment

12. Chapter 12: Jakarta Enterprise Beans

13. Chapter 13: Jakarta Messaging

14. Chapter 14: Web Services with Jakarta XML Web Services

15. Chapter 15: Putting it All Together

16. Index

Why subscribe?

17. Other Books You May Enjoy

An introduction to microservices

Architecting applications as a series of microservices offers some advantages over traditionally designed applications, as well as some disadvantages. When considering a microservices architecture for our applications, we must carefully weigh the advantages and disadvantages before we make our decision.

The advantages of a microservices architecture

Developing an application as a series of microservices offers several advantages over traditionally designed applications, such as the following:

Smaller code bases: Since each microservice is a small, standalone unit, code bases for microservices tend to be smaller and easier to manage than traditionally designed applications.
Microservices encourage good coding practices: A microservices architecture encourages loose coupling and high cohesion.
Greater resilience: Traditionally designed applications act as a single point of failure; if any component of an application is down or unavailable...