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


Some years ago, the software industry used the waterfall model to manage the systems development lifecycle (SDLC). The waterfall model includes many phases, such as gathering requirements, designing a solution, writing the code, verifying that the code meets the user requirements, and finally, delivering the product. In order to work on each of these phases, different teams and roles were created, including analysts, developers, software architects, QA teams, operations people, project managers, and so on. Each one of these roles were responsible for producing output and delivering it to the next team.

The steps needed to create a software system using the waterfall model are as follows:

  1. Analysts gather the software requirements
  2. Software architects review the requirements carefully and expand the documents with information about the tools and technologies that will be used, modules that have to be written to create the system, diagrams showing how the components are going to be connected...