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

Preparing BrownField PSS services

In the previous section, we successfully set up Mesos and Marathon. In this section, we will see how to deploy the BrownField PSS application previously developed using Mesos and Marathon.


The full source code of this chapter is available under the chapter10 projects in the code files under Copy chapter9.* into a new STS workspace and rename it chapter10.*.

In this example, we will force the Mesos cluster to bind to fixed ports, but, in an ideal world, we will delegate the Mesos cluster to dynamically bind services to ports. Also, since we are not using a DNS or HA Proxy, we will hardcode the IP addresses. In the real world, a VIP for each service will be defined, and that VIP will be used by the services. This VIP will be resolved by the DNS and Proxy.

Perform the following steps to change the BrownField application to run on AWS:

  1. Update search microservices ( to reflect the RabbitMQ...