Book Image

Java EE 8 High Performance

By : Romain Manni-Bucau
Book Image

Java EE 8 High Performance

By: Romain Manni-Bucau

Overview of this book

The ease with which we write applications has been increasing, but with this comes the need to address their performance. A balancing act between easily implementing complex applications and keeping their performance optimal is a present-day need. In this book, we explore how to achieve this crucial balance while developing and deploying applications with Java EE 8. The book starts by analyzing various Java EE specifications to identify those potentially affecting performance adversely. Then, we move on to monitoring techniques that enable us to identify performance bottlenecks and optimize performance metrics. Next, we look at techniques that help us achieve high performance: memory optimization, concurrency, multi-threading, scaling, and caching. We also look at fault tolerance solutions and the importance of logging. Lastly, you will learn to benchmark your application and also implement solutions for continuous performance evaluation. By the end of the book, you will have gained insights into various techniques and solutions that will help create high-performance applications in the Java EE 8 environment.
Table of Contents (12 chapters)

The application architecture

Our application will import some stock quotations daily; it will then expose them and allow you to update them through a web service.

To implement it, we will use a standard Java EE architecture:

  • The persistence layer will use JPA 2.2 and store the data in a MySQL database.
  • A service layer will implement the business logic and orchestrate the persistence layer. It will rely on the following:
    • Java Transaction API (JTA) 1.2 for transactionality
    • Context and Dependency Injection 2.0 (CDI) for Inversion of Control (IoC)
    • Bean Validation 2.0 for validations
  • A front layer will expose a part of the service layer through HTTP. It will rely on the following:
    • JAX-RS 2.1 for stateless endpoints
    • WebSocket 1.1 for stateful communications
    • JSON-B 1.0 for marshalling/unmarshalling

Here is a picture summarizing this structure: