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

User interface architecture – backend versus frontend

It may seem silly to discuss where a User Interface (UI) must live. After all, it's almost a given – the UI is the forefront of our software architecture, providing the interaction with end users, and for this reason, it must stay at the front, hence the term frontend, which is used as a synonym for UI. And everybody agrees on that, without a doubt.

Except that it's not that easy to draw a line as to where a UI starts and where it ends. And, depending on the particular implementation, a number of different components may provide the functionalities needed to build the experience we want to eventually present to our customers. The UI will be made of, more or less, the following components:

  • Assets, also referred to as static files: These are the pieces of the web application that must be sent (where relevant) to our clients. They include, usually, HTML files, JavaScript scripts, other graphical artifacts...