Book Image

Hands-On Software Architecture with Java

By : Giuseppe Bonocore
5 (1)
Book Image

Hands-On Software Architecture with Java

5 (1)
By: Giuseppe Bonocore

Overview of this book

Well-written software architecture is the core of an efficient and scalable enterprise application. Java, the most widespread technology in current enterprises, provides complete toolkits to support the implementation of a well-designed architecture. This book starts with the fundamentals of architecture and takes you through the basic components of application architecture. You'll cover the different types of software architectural patterns and application integration patterns and learn about their most widespread implementation in Java. You'll then explore cloud-native architectures and best practices for enhancing existing applications to better suit a cloud-enabled world. Later, the book highlights some cross-cutting concerns and the importance of monitoring and tracing for planning the evolution of the software, foreseeing predictable maintenance, and troubleshooting. The book concludes with an analysis of the current status of software architectures in Java programming and offers insights into transforming your architecture to reduce technical debt. By the end of this software architecture book, you'll have acquired some of the most valuable and in-demand software architect skills to progress in your career.
Table of Contents (20 chapters)
1
Section 1: Fundamentals of Software Architectures
7
Section 2: Software Architecture Patterns
14
Section 3: Architectural Context

Summary

In this chapter, we have looked at some interesting considerations about monitoring and tracing our applications.

We started by reviewing some basic concepts about logging in Java, and why log aggregation is a good thing to do in microservices and cloud-native applications. We then moved on to the concept of metrics and health checks, and how applications can provide data in real time on the performance and health of our modules.

We then discussed tracing, which is very important when it comes to troubleshooting and managing distributed applications (such as microservices applications). APM was the next topic and is about putting all the information together (such as metrics, health checks, and logs) to create an overview of the application insights.

Last but not least, we saw how service monitoring involves linking business information with the technical KPIs behind it, to support troubleshooting and draw more insights from the collected data.

In the next chapter...