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 an automated pipeline for microservices

Maybe you are wondering, why is there an automation recipe in a Jakarta EE 8 book? or even, is there any specification under Jakarta EE 8 that defines pipeline automation?

The answer to the second question is no. At least no at this very moment. The answer to the first one I'll explain here.

Many times at conferences I am asked the question, how do I migrate my monolith to microservices? It comes in some variations, but at the end of the day, the question is the same.

People want to do it for different reasons:

  • They want to keep up with the trend.
  • They want to scale an application.
  • They want to be able to use different stacks under the same solution.
  • They want to look cool.

Any of these reasons are OK, and you can justify your migration to microservices with any of them if you want although I would question the real motivation...