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

Case studies and examples

In this chapter, as in previous ones, we will continue our study of the mobile payments application. We will keep exploring this context to see some examples of the diagrams we have discussed so far.

UML class diagrams for mobile payments

As a first example, we will look at UML class modeling. This is a very common diagram in Java projects. It is debated whether it's useful to build and maintain documentation that is so close to code (see also the considerations we discussed in the section on C4), since it may be seen as not adding that much value and being hard to maintain. Moreover, in modern development models (such as cloud-native and microservices), you are supposed to communicate between parts of the application by using established interfaces (such as REpresentational State Transfer (REST) or Google Remote Procedure Call (gRPC) and avoid exposing the internal model of your applications for others to tap into.

My personal view is that the...