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

Container orchestration with Kubernetes

Kubernetes introduces a new set of concepts for an environment working with Docker containers. We could say that Kubernetes does in production what Docker Compose does in development, but there is much more to it than that. Kubernetes is an open source system originally created for Google Cloud Engine, but you can use it with AWS or any other cloud provider. It is intended for remotely managing Docker clusters in different environments.

Kubernetes introduces the following main concepts:

  • Pods
  • Replication controllers
  • Services
  • Labels


The pod is a new concept introduced by Kubernetes. A pod is comprised of a group of related containers that represent a specific application. This is the most basic unit within Kubernetes; you don't have to keep thinking about containers because pods are what you should focus on here.

Let's consider an application called XYZ that stores its information in a database that exposes a REST API that is consumed by its UI, as shown...