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%

Failover

In a distributed system, it is very important to ensure that you know how to handle failures. Java EE applications being more and more connected to other systems, they face this challenge more and more, so it is important to know how you will deal with failover when it happens.

The first meaning of failover is, indeed, to fail over. It can be rephrased as the capability to switch to a backup system when the primary system fails. In Java EE applications, there are lots of places where this can be set up, but they are all related to external systems:

Databases: If a database connection fails, how to still handle the requests?
JMS: If a broker fails, what to do?
Other network API (such as SOAP or REST API): If the remote server is down, what to do?
WebSocket: If the target server closes the connection or fails, what to do?

In general, each time your application relies...