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


As we have seen, Docker helps us to reproduce the setup used to deploy an application, but it also helps us to distribute the application to be used in different environments. This task can be performed using registries.

A registry is a service that is responsible for hosting and distributing Docker images. The default registry used by Docker is Docker Hub. There are other options available on the market that can be used as Docker registries, including the following:

  • Quay
  • Google Container Registry
  • AWS Container Registry

Docker Hub is really popular because it works in ways that you do not even notice. For instance, if you're creating a container and the image doesn't exist in your local repository, it will automatically download the image from Docker Hub. All the existing images are created by someone else and published in these registries. In the same way, we can publish our own images in order to make them available to other people within an organization by using private repositories...