Book Image

Software Architecture with Spring 5.0

By : René Enríquez, Alberto Salazar
Book Image

Software Architecture with Spring 5.0

By: René Enríquez, Alberto Salazar

Overview of this book

Spring 5 and its ecosystem can be used to build robust architectures effectively. Software architecture is the underlying piece that helps us accomplish our business goals whilst supporting the features that a product demands. This book explains in detail how to choose the right architecture and apply best practices during your software development cycle to avoid technical debt and support every business requirement. Choosing the right architecture model to support your business requirements is one of the key decisions you need to take when a new product is being created from scratch or is being refactored to support new business demands. This book gives you insights into the most common architectural models and guides you when and where they can be used. During this journey, you’ll see cutting-edge technologies surrounding the Spring products, and understand how to use agile techniques such as DevOps and continuous delivery to take your software to production effectively. By the end of this book, you’ll not only know the ins and outs of Spring, but also be able to make critical design decisions that surpass your clients’ expectations.
Table of Contents (21 chapters)
Title Page
Copyright and Credits
Packt Upsell

Why performance matters

Over the last two decades as a consultant, I visited several government institutions, banks, and financial institutions, establishing a common factor for a lack of performance in applications that are working in production, and I found common issues that can be avoided if you use a set of good practices as part of your SDLC.

It's important to pay close attention to performance, because it brings huge trouble to companies, project sponsors, and customers since an application that faces this problem brings dissatisfaction on several levels.

Before giving recommendations, we are going to review and understand the non-functional requirements of scalability, availability, and performance.


This describes the capacity of a system to deal with to a high workload and to increase its capacity in order to resolve more requests based on the demand for work.

Horizontal scalability

This is resolved by adding additional nodes with all the functionality of your system, redistributing...