Book Image

Java EE 8 Cookbook

By : Elder Moraes
Book Image

Java EE 8 Cookbook

By: Elder Moraes

Overview of this book

Java EE is a collection of technologies and APIs to support Enterprise Application development. The choice of what to use and when can be dauntingly complex for any developer. This book will help you master this. Packed with easy to follow recipes, this is your guide to becoming productive with Java EE 8. You will begin by seeing the latest features of Java EE 8, including major Java EE 8 APIs and specifications such as JSF 2.3, and CDI 2.0, and what they mean for you. You will use the new features of Java EE 8 to implement web-based services for your client applications. You will then learn to process the Model and Streaming APIs using JSON-P and JSON-B and will learn to use the Java Lambdas support offered in JSON-P. There are more recipes to fine-tune your RESTful development, and you will learn about the Reactive enhancements offered by the JAX-RS 2.1 specification. Later on, you will learn about the role of multithreading in your enterprise applications and how to integrate them for transaction handling. This is followed by implementing microservices with Java EE and the advancements made by Java EE for cloud computing. The final set of recipes shows you how take advantage of the latest security features and authenticate your enterprise application. At the end of the book, the Appendix shows you how knowledge sharing can change your career and your life.
Table of Contents (14 chapters)

Building an automated pipeline for microservices

Maybe you are wondering, "why is there an automation recipe in a Java EE 8 book?", or even, "is there any specification under Java EE 8 that defines a 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 in 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 work with something that looks like a new fashion
  • 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...