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

Application Performance Management

APM is a broad and very important aspect of running an application in production. It involves a lot of different technologies, and sometimes it has some unknowns around log aggregation, metrics collection, and overall monitoring, among other things.

Each vendor or stack of monitoring technologies has slightly different comprehensions of what APM is about, and somewhat different implementations of it as a result.

I think that it's good to start from the goal: the goal of APM is to have insights into how a set of applications is performing, and what impact the underlying parameters (such as memory usage, database metrics, and more) have on the end user experience (such as user interface responsiveness, response times, and so on).

It is easy to understand that to implement such a useful (and broad) goal, you may need to stack a number of different tools and frameworks.

We have seen some of this in the previous section: you may want...