Java EE 8 High Performance

Troubleshooting performance measures and optimizations for your Java EE Applications

Ratings 3.81 / 5.00

What You Will Learn!

Optimize your Java Enterprise application by introducing asynchronous behavior
Use new features added in Java SE and EE 8
Proactively monitor the performance and state of your system
Analyse and visualize key performance metrics
Conduct Load and Stress tests to check for hidden bottlenecks or errors in your application
Add a cache to your system or applying libraries for real-time and high-performance
Optimize your Java EE applications

Description

Java EE 8 High Performance aims how to use Java EE for mission- or performance-critical applications. How to monitor the state and performance metrics of your program in a distributed environment. To make use of concurrency and multiple cores provided by modern processor architectures plus the support offered by Java 8. Common pitfalls and How you can scale your application to meet higher demand by adding cluster and load-balancing techniques. As well as optimization tools and frameworks like the Java Cache standard, Eclipse Collections or Javolution.

About the Author

Werner Keil is a Cloud Architect, Java EE, and Microservice expert for a large bank. He has helped Global 500 Enterprises across industries and leading IT vendors.

He worked for 3 decades as IT Manager, PM, Coach, SW architect and consultant for Finance, Mobile, Media, Transport and Public sector. He develops enterprise systems using Java, Java EE/Jakarta EE, other Oracle, IBM or Microsoft technologies, JavaScript, Node, Angular, dynamic or various functional languages.

Werner is Committer at Apache Foundation, Eclipse Foundation, Babel Language Champion, UOMo Project Lead and active member of the Java Community Process in JSRs like 321 (Trusted Java), 331 (CP), 344 (JSF 2.2), 354 (Money), 358/364 (JCP.next), 360/361 (ME Embedded), 362 (Portlet 3), 363 (Unit-API, also Spec Lead), 365 (CDI 2), 366 (Java EE 8), 375 (Java EE Security), 380 (Bean Validation 2), 382 (Config), 385 (Unit-API 2, also Spec Lead) and was the only Self-employed Member of the Executive Committee for 9 years in a row