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

Implementing microservices

Now that we have a good understanding of what microservices are and what they are intended for, we are going to start looking at how to implement a microservice architecture using Spring Framework. Over the next few sections, we are going to look at some of the important concepts that we haven't covered so far. It's better to approach these from a practical viewpoint to make them easier to understand.

Dynamic configuration

We have all worked on applications that use different configuration files or associated metadata to allow you to specify configuration parameters that make an application work. When we are talking about microservices, we need to approach this configuration process in a different way. We should avoid configuration files and instead adopt the twelve-fact app configuration style (as outlined at, proposed by Heroku. When we are using this configuration style, we want to externalize all the properties that are different in each...