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

Introducing single-page applications

Single-Page Applications (or SPAs) is a broad term that came about to simply describe the behavior of some solutions meant to create web UIs in a lighter, more modern way. The first characteristic of the SPA is the one that it relates to the name. An SPA, in general, bundles all the assets necessary to start user interaction into a single HTML document and sends it to the client.

All the following interactions between the client and the server, including loading data, sending data back, and loading other assets (as images or CSS files), are performed within the page using JavaScript. For this reason, SPAs minimize the communication between the client and server (improving performances), avoid the full-page refresh, and allow for a simpler architectural model.

Indeed, a basic, static file-serving web server (such as Apache HTTPD or NGINX) is all you need on the frontend (no Java application server is needed). Moreover, the interaction between...