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


Every single application is created to solve specific business requirements and accomplish certain business goals, so it is essential to assess on a regular basis an application to verify whether these goals are being accomplished. As part of this verification process, we want to measure the health and performance of our application using metrics that can give us insights into the following factors:

  • Application Monitoring: When we are talking about the health of an application, it is important to know the amount of resources that are being used, such as CPU, memory consumption, threads, or I/O processes. Recognizing potential errors and bottlenecks is important to know whether or not we need to scale, tune, or refactor our code.
  • Business Monitoring: These metrics are helpful to understand key business indicators about the business itself. For example, if we have an online store, we want to know whether or not we are accomplishing the established sales goals, or in a banking application...