Book Overview & Buying
Table Of Contents
Feedback & Rating

Java EE 8 High Performance

By : Romain Manni-Bucau

3.9 (36)

Buy this Book

Java EE 8 High Performance

3.9 (36)

By: Romain Manni-Bucau

Buy this Book

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.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Money – The Quote Manager Application

Setting up the environment

The application architecture

Application project highlights

Application summary

The application server

Testing the application

Setting up MySQL

Conclusion

Summary

Looking Under the Cover – What is This EE Thing?

Context and Dependency Injection – what did you do to my beans?

JAX-RS – the servlet router

JPA – the database link

The Java Transaction API

Server resources

Java EE and performances

Summary

Monitor Your Application

Java tools to know what my application is doing

GlassFish ad hoc monitoring

Libraries monitor your application

Summary

Application Optimization – Memory Management and Server Configuration

Java and the memory

Java EE and the resources

Summary

Scale Up – Threading and Implications

Java EE threading model

Thread data and consistency

Java EE and threads

Reactive programming and Java EE

Summary

Be Lazy; Cache Your Data

Caching challenges

HTTP and caching

JCache – the standard cache of Java EE

Cache once

Summary

Be Fault-Tolerant

It will fail, no doubt!

Load balancing – pick the best one

Failover

Bulk head

Timeouts

Summary

Loggers and Performances – A Trade-Off

I log, you log, they log

Logging frameworks and concepts

Logging invocations

Logging patterns

Logging implementations – which one to pick

Summary

Benchmarking Your Application

Benchmarking – validating your application against your SLA

Preparing your benchmark

Benchmark iterations

After your benchmark

Summary

Continuous Performance Evaluation

Writing performance tests – the pitfalls

Writing performance tests

Continuous integration platform and performance

Summary

Another Book You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

3.9 (36)

5 star

36.1%

4 star

41.7%

3 star

11.1%

2 star

2.8%

1 star

8.3%

JPA – the database link

The Java Persistence API (JPA) is the link to the database (MySQL for our quote application we created in chapter 1). Its goal is to enable an application to map the database model to Java objects. The gain is that we can use the database as any object.

For instance, consider the following table, which matches our quote representation in the database:

The preceding table can be converted into the following object in Java, thanks to JPA annotations:

While the tables are flat, mapping them in JPA is pretty straightforward, but the more the model complexity will increase, the more you will realize the two opposed worlds: building a great Java model can lead to an awful database model or the opposite. Why? Because both don't share exactly the same philosophy and can lead to some anti-patterns.

For instance, in our model, we linked our Quote to...