Book Image

Building Microservices with Spring

By : Dinesh Rajput, Rajesh R V
Book Image

Building Microservices with Spring

By: Dinesh Rajput, Rajesh R V

Overview of this book

Getting Started with Spring Microservices begins with an overview of the Spring Framework 5.0, its design patterns, and its guidelines that enable you to implement responsive microservices at scale. You will learn how to use GoF patterns in application design. You will understand the dependency injection pattern, which is the main principle behind the decoupling process of the Spring Framework and makes it easier to manage your code. Then, you will learn how to use proxy patterns in aspect-oriented programming and remoting. Moving on, you will understand the JDBC template patterns and their use in abstracting database access. After understanding the basics, you will move on to more advanced topics, such as reactive streams and concurrency. Written to the latest specifications of Spring that focuses on Reactive Programming, the Learning Path teaches you how to build modern, internet-scale Java applications in no time. Next, you will understand how Spring Boot is used to deploying serverless autonomous services by removing the need to have a heavyweight application server. You’ll also explore ways to deploy your microservices to Docker and managing them with Mesos. By the end of this Learning Path, you will have the clarity and confidence for implementing microservices using Spring Framework. This Learning Path includes content from the following Packt products: • Spring 5 Microservices by Rajesh R V • Spring 5 Design Patterns by Dinesh Rajput
Table of Contents (22 chapters)
Title Page
About Packt

DevOps, Cloud, and Containers

The trios Cloud (more specifically, Containers), Microservices and DevOps, are targeting a set of common objectives--speed of delivery, business value, and cost benefits. All three can stay evolved independently, but they complement each other to achieve the desired common goals. Organizations embarking on any of these naturally tend to consider the others as they are closely linked together:

Many organizations start their journey with DevOps as an organizational practice to achieve high velocity release cycles, but eventually move to microservices architecture and cloud. However, it is not mandatory to have microservices and Cloud to support DevOps. However, automating release cycles of large monolithic applications does not make much sense, and, in many cases, it would be impossible to achieve. In such scenarios, microservices architecture and Cloud will be handy when implementing DevOps.

If we flip the coin, Cloud does not need a microservices architecture...