Book Image

Jakarta EE Cookbook - Second Edition

By : Elder Moraes
Book Image

Jakarta EE Cookbook - Second Edition

By: Elder Moraes

Overview of this book

Jakarta EE is widely used around the world for developing enterprise applications for a variety of domains. With this book, Java professionals will be able to enhance their skills to deliver powerful enterprise solutions using practical recipes. This second edition of the Jakarta EE Cookbook takes you through the improvements introduced in its latest version and helps you get hands-on with its significant APIs and features used for server-side development. You'll use Jakarta EE for creating RESTful web services and web applications with the JAX-RS, JSON-P, and JSON-B APIs and learn how you can improve the security of your enterprise solutions. Not only will you learn how to use the most important servers on the market, but you'll also learn to make the best of what they have to offer for your project. From an architectural point of view, this Jakarta book covers microservices, cloud computing, and containers. It allows you to explore all the tools for building reactive applications using Jakarta EE and core Java features such as lambdas. Finally, you'll discover how professionals can improve their projects by engaging with and contributing to the community. By the end of this book, you'll have become proficient in developing and deploying enterprise applications using Jakarta EE.
Table of Contents (14 chapters)

Building Lightweight Solutions Using Microservices

Microservices is one of the top buzzwords nowadays. It's easy to understand why— in the growing

software industry, where the amount of services, data, and users is increasing exponentially, we need a way to build and deliver faster, decoupled, and scalable solutions.

Why are microservices good? Why use them? With growing demand, the need to deal with each module separately has increased. For example, in your customer application, perhaps user information needs to be scaled differently from the address information.

In the monolith paradigm, you need to deal with it atomically—you build a cluster for the whole application or you scale your entire host up (or down). The problem with this approach is that you can't focus your effort and resources on a specific feature, module, or function— you are always...