Learn Microservices with Spring Boot - Chapter 8a (1/4)
This repository contains the source code of the practical use case described in the book Learn Microservices with Spring Boot (2nd Edition).
The book follows a pragmatic approach to building a Microservice Architecture. You start with a small monolith and examine the pros and cons that come with a move to microservices.
Chapter 8 version 1/4
The Chapter 8's source code is divided into four parts for a better understanding of how the system evolves when we start introducing Common Patterns in Microservice Architectures.
In this first part, we introduce the Gateway pattern, that helps abstracting the internal architecture from the outside by routing external requests to the corresponding microservice. In the next iteration (2/4), we'll also add Service Discovery and Load Balancing.
The main concepts included in this first part of the chapter are:
- Why do we need a Gateway? The problem, explained.
- The Gateway Pattern: how it works.
- Spring Cloud Gateway: core concepts.
- A practical implementation of the Gateway, going through the required changes and additions to our code.
As usual, the book follows a hands-on approach, so you learn everything based on this microservice case study.
Check the Book's Web Page to see the complete list of chapters.
Running the app
- JDK 14+
- Node.js v13.10+
- npm 6.13.7+
- RabbitMQ 3.8.3+
- You need a RabbitMQ server running. Run the server according to the instructions for your OS, for example:
- To start the Multiplication microservice, you can use the command line with the included Maven wrapper:
multiplication$ ./mvnw spring-boot:run
- To start the Gamification microservice, you do the same from its corresponding folder:
gamification ./mvnw spring-boot:run
- To start the Gateway microservice, you do the same from its corresponding folder:
gamification ./mvnw spring-boot:run
- The React application can be started with npm. First, you need to download the dependencies with:
challenges-frontend$ npm install
- Then, you start the server with:
challenges-frontend$ npm start
In the final version of our code, we use Docker to start our complete system easily. However, it's not yet introduced at this point in the book, so we're starting all these components manually.
Once the backend and the fronted are started, you can navigate to
http://localhost:3000 in your browser and start resolving multiplication challenges. From the user's perspective, there are no differences between this version and the one we completed in Chapter 7. We do know that all requests are now going through the Gateway service, and we gained some new advantages as detailed in the book.
- Do you have questions about how to make this application work?
- Did you get the book and have questions about any concept explained within this chapter?
- Have you found issues using updated dependencies?
Don't hesitate to create an issue in this repository and post your question/problem there.
About the book
Are you interested in building a microservice architecture from scratch? You'll face all the challenges of designing and implementing a distributed system one by one, and will be able to evaluate if it's the best choice for your project.
Visit https://tpd.io/book-extra for all the details about the book.
You can buy the book online from these stores:
Source code by chapter (all repositories are available on Github)
- Chapter 3. A professional 3-tier 3-layer Spring Boot app
- Chapter 4. Building a basic frontend in React (backender-friendly)
- Chapter 5. The Data Layer Concepts and Spring Data JPA
- Chapter 6. Starting with Microservices - Synchronous
- Chapter 7. Event-Driven Architectures - Making our system asynchronous
- Chapter 8 (I). The Gateway Pattern in Microservice Architectures (Spring Cloud Gateway)
- Chapter 8 (II). Service Discovery and Load Balancing for Spring Boot Microservices (Consul / Spring Cloud Load Balancer)
- Chapter 8 (III). Centralized Configuration with Consul KV
- Chapter 8 (IV). Centralized Logs, Distributed Tracing, and Containerization with Docker (Buildpacks) and Docker Compose