KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#developer-tools #typescript #dsh #dsh-plugin #ai-agent #codex #ai-agents #deepseek-harness #claude-code #cli #react #mcp

Software-Architecture-with-Spring

★ 42 Open GitHub ↗

Software Architecture with Spring, published by Packt

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# 🏗️ Software Architecture with Spring 
**Design scalable and high-performance Java applications with Spring**

<table style="border: none;">
  <tr>
    <td><img src="book-cover.png" alt="Software Architecture with Spring" width="250"/></td>
    <td style="vertical-align: top; padding-left: 20px;">
      <ul>
        <li>🔗 <strong><a href="https://www.packtpub.com/en-us/product/software-architecture-with-spring-9781835880609?utm_medium=affiliate&utm_campaign=eb8fa252-e255-175d-1cc7-659b7b674281&utm_term=e2025f61-d111-eb11-a812-00224801bc77&utm_content=B22261">Buy on Packt</a></strong></li>
        <li>🛒 <strong><a href="https://packt.link/P1FKw">Buy on Amazon</a></strong></li>
      </ul>
    </td>
  </tr>
</table>

Welcome to the repository for **"Software Architecture with Spring"**! This book is a practical guide for software engineers, architects, and developers looking to master modern software architecture principles, especially in the context of Java and Spring Framework.

## 🔍 Overview

This book explores the journey of building robust, scalable, and maintainable applications using a structured approach. It covers a wide range of architectural styles and design principles, equipping readers with insights and strategies for architecting resilient systems. From monolithic applications to microservices, this guide walks through key concepts and provides actionable examples to enhance your software architecture skills.

## 🛠️ Tools to Follow Along the Examples

### 💻 IDEs
- [IntelliJ](https://www.jetbrains.com/idea/download) – JetBrains Java IDE
- [Spring Tools](https://spring.io/tools) – Spring-based Eclipse distribution
- [Visual Studio Code](https://code.visualstudio.com/download) – Lightweight code editor

### 🗄️ Database Clients
- [DBeaver](https://dbeaver.io/) – Universal database client
- [Compass](https://www.mongodb.com/try/download/compass) – MongoDB GUI
- [DataGrip](https://www.jetbrains.com/datagrip/download) – JetBrains SQL IDE
- [Redis Insight](https://redis.io/insight/) – GUI for visualizing Redis data and performance

### 📬 Kafka Client
- 🛠️ [Kafka Tool](https://kafkatool.com/download.html) – GUI for managing and browsing Kafka clusters

### 🔌 API Testing Tools
- [Postman](https://www.postman.com/downloads/) – API platform for building and testing APIs

### 🧪 Performance Testing Tools
- [Apache JMeter](https://jmeter.apache.org/download_jmeter.cgi) – Load testing tool for analyzing and measuring performance

### 🧰 Monitoring & Profiling
- [VisualVM](https://visualvm.github.io/download.html) – Java profiler and monitoring tool

## 🐳 Containerization
- [Docker](https://www.docker.com/get-started/) – Container platform for building and running applications

## ☸️ Kubernetes Tools
- [MiniKube](https://minikube.sigs.k8s.io/docs/start) - Tool to run a local Kubernetes cluster for learning and development

## 🤖 Jenkins
- [Jenkins](https://www.jenkins.io/download/) – Automation server for building, testing, and deploying software

## 🌐 ngrok
- [ngrok](https://ngrok.com/download) – Secure tunnel for exposing local servers to the public internet

## 🐙 GitHub
- [GitHub](https://github.com/) – Platform for hosting and collaborating on code using Git version control

### Sample Code

The book provides sample code for each major chapter, allowing readers to experiment and implement concepts in real-world scenarios. Please check each chapter's directory for related code snippets and explanations.

## 📘 Chapter 1: Diving into the Software Architecture
  The examples provided delve into fundamental architectural concepts, such as high and low coupling, cohesion, and the SOLID principles.

### 📁 Folder Structure

```
  ch1/
  ├── 01-high-coupling-shopping-application/           # Example with high coupling
  ├── 02-low-coupling-shopping-application/            # Example with low coupling
  ├── 03-low-cohesion-usermanagement-application/      # Example with low cohesion
  ├── 04-high-cohesion-usermanagement-application/     # Example with high cohesion
  ├── 05-solid-srp-library-application/                # SRP - Single Responsibility Principle
  ├── 06-open-closed-library-application/              # OCP - Open/Closed Principle
  ├── 07-liskov-substitution-library-application/      # LSP - Liskov Substitution Principle
  ├── 08-interface-segregation-library-application/    # ISP - Interface Segregation Principle
  └── 09-dependency-inversion-library-application/     # DIP - Dependency Inversion Principle
```

## 📦 Chapter 4: Monolithic Architecture

### 📁 Folder Structure

```
ch4/
├── docker-resources/
│   ├── postgresql/
│   │   └── init.sql        # SQL DDL and DML
│   ├── .env                # PostgreSQL credentials
│   └── docker-compose.yml # Runs PostgreSQL and populates data
└── onlineauction/          # Source code application
```
  ### ⚙️ Prerequisites
    - ☕ Java 21  
    - 🐳 Docker & Docker Compose  
    - 🧰 Maven 3.9.9

### 🚀 Setup Instructions

#### 🐳 Spin up PostgreSQL with Docker
    1. Go the docker ch4/docker folder
    2. Execute the command: ```docker-compose up -d```

#### 🧱 Build & Run the Application
    3. Go to the project's folder: onlineauction
    4. Execute the command: ```mvn clean package```
    5. To run the project execute the command:  ```mvn spring-boot:run```

### 🌐 Accessing the Application
    6. Open your browser and go to http://localhost:8080
    7. Click on the Login menu  
    8. Use one of the following credentials:
       👑 Administrator : 
          Username: admin - Password: test123
       🧑‍💻 User:
          Username: user - Password: test123
  
  ### 🔗 Database Connection Details

- **URL**: `jdbc:postgresql://localhost:5432/auction_db`  
  - **User**: `auction_app`  
  - **Password**: `auction123`  
  - **Database**: `auction_db`

## 📦 Chapter 5: Client-Server Architecture

### 📁 Folder Structure

```
ch5/
├── docker-resources/
│   ├── postgresql/
│   │   └── init.sql              # SQL DDL and DML scripts
│   ├── .env                      # PostgreSQL credentials
│   └── docker-compose.yml        # Spins up PostgreSQL and populates data
├── onlineauction/                # Server application
├── onlineauction-client-mobile/  # Mobile client application
└── onlineauction-client-web/     # Web client application
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9  
- 🌐 Node.js and npm  
- ⚛️ React  
- 📱 React Native  
- 📲 Expo Go App

---

### 🚀 Setup Instructions

#### 🐳 Set Up and Run the Server

1. Navigate to the Docker folder: ch5/docker-resources
2. Start the containers:  
   ```bash
   docker-compose up -d
   ```
3. Navigate to the server project folder: ch5/onlineauction-server
4. Build the application:  
   ```bash
   mvn clean package
   ```
5. Run the application:  
   ```bash
   mvn spring-boot:run
   ```
6. Access OpenAPI documentation:  
   [http://localhost:8080/swagger-ui/index.html](http://localhost:8080/swagger-ui/index.html)

7. Credentials to generate a token:
   - 👑 **Administrator**  
     - Username: `admin`  
     - Password: `test123`  
   - 🧑‍💻 **User**  
     - Username: `user`  
     - Password: `test123`

### 🔗 Database Connection Details

- **URL**: `jdbc:postgresql://localhost:5432/auction_db`  
  - **User**: `auction_app`  
  - **Password**: `auction123`  
  - **Database**: `auction_db`

---

#### 🌐 Run the Web Client

1. Navigate to the web client folder: ch5/onlineauction-client-web

2. Install dependencies:  
   ```bash
   npm install
   ```
3. Start the application:  
   ```bash
   npm start
   ```
4. Access the web app at:  
   [http://localhost:3000](http://localhost:3000)

5. Use the following credentials to log in:  
   - 👑 **Administrator**  
     - Username: `admin`  
     - Password: `test123`  
   - 🧑‍💻 **User**  
     - Username: `user`  
     - Password: `test123`

---

#### 📱 Run the Mobile Client

1. Navigate to the mobile client folder: ch5/onlineauction-client-mobile  
2. Install Expo CLI globally (you may need to use sudo):  
   ```bash
   npm install -g expo-cli
   ```
3. Install project dependencies:  
   ```bash
   npm install
   ```
4. Fix dependencies (if needed):  
   ```bash
   expo doctor --fix-dependencies
   ```
5. Check configuration:  
   ```bash
   npx expo-doctor
   ```
6. Install required dependencies:  
   ```bash
   npx expo install --check
   ```
7. Update Expo:  
   ```bash
   npm install expo@latest
   ```
8. Install Expo Metro runtime:  
   ```bash
   npx expo install @expo/metro-runtime
   ```
9. Start the app:  
   ```bash
   npx expo start
   ```
10. Press `w` to open the app in the browser, or scan the QR code with Expo Go.

11. Use the following credentials to log in:  
   - 👑 **Administrator**  
     - Username: `admin`  
     - Password: `test123`  
   - 🧑‍💻 **User**  
     - Username: `user`  
     - Password: `test123`

---

> 📝 **Note**: Some commands may not be necessary, but following these steps ensures the app runs on Expo Go.

Here’s the formatted content for Chapter 6: Microservices Architecture in the same style as your Chapter 5 section. You can copy and paste it directly into your README.md:

## 🧩 Chapter 6: Microservices Architecture

### 📁 Folder Structure
```
ch6/
├── docker/
│   ├── postgresql/
│   │   └── init.sql               # SQL DDL and DML scripts
│   ├── mongo-init/
│   │   └── init.js                # MongoDB: create DB, collections, insert data
│   ├── .env                       # PostgreSQL and MongoDB credentials
│   └── docker-compose.yml        # Spins up PostgreSQL, MongoDB, and all microservices
├── docker-resources/
│   ├── postgresql/
│   │   └── init.sql               # SQL DDL and DML scripts
│   ├── mongo-init/
│   │   └── init.js                # MongoDB: create DB, collections, insert data
│   ├── .env                       # PostgreSQL and MongoDB credentials
│   └── docker-compose.yml        # Spins up databases and populates data for IDE execution
├── postman/
│   └── ch6.postman_collection.json  # Postman collection to test all services
├── authentication-services/      # Authentication microservice
├── user-services/                # User microservice
└── product-services/             # Product microservice
```

### ⚙️ Prerequisites
	•	☕ Java 21
	•	🐳 Docker & Docker Compose
	•	🧰 Maven 3.9.9

### 🚀 Setup Instructions

#### 👨‍💻 Run Microservices via IDE
1.	Navigate to the Docker folder: ch6/docker-resources
2.	Start the containers:

```
docker-compose up -d
```

3.	Open the microservices (authentication-services, user-services, product-services) in your IDE
4.	For each microservice, run the following commands:
```  
mvn clean package
mvn spring-boot:run
```
5.	Navigate to the postman folder and import the collection ch6.postman_collection.json [Postman Import Documentation](https://learning.postman.com/docs/getting-started/importing-and-exporting/importing-data/)
6.	Use Postman to trigger requests to the microservices
7.  Use the following credentials to generate the token:  
   - 👑 **Administrator**  
     - Username: `admin@wxauction.com`  
     - Password: `test123`  
   - 🧑‍💻 **User**  
     - Username: `user@wxauction.com`  
     - Password: `test123`

#### 🛠️ Run All Services Without Code (Using Prebuilt Images)

1. Navigate to the Docker folder: ch6/docker
2. Start the containers:
```
  docker-compose up -d
```
3. Navigate to the postman folder and import the collection ch6.postman_collection.json
4. Use Postman to trigger requests to the microservices
5. Use the following credentials to generate the token:  
   - 👑 **Administrator**  
     - Username: `admin@wxauction.com`  
     - Password: `test123`  
   - 🧑‍💻 **User**  
     - Username: `user@wxauction.com`  
     - Password: `test123`

### 📄 Swagger API Documentation

- 🔐 **Authentication Service**: [localhost:8081/swagger-ui/index.html](http://localhost:8080/swagger-ui/index.html)
- 👤 **User Service**: [localhost:8081/swagger-ui/index.html](http://localhost:8081/swagger-ui/index.html)
- 📦 **Product Service**: [localhost:8082/swagger-ui/index.html](http://localhost:8082/swagger-ui/index.html)

### 🔗 Database Connection Details
	•	PostgreSQL
	•	🛢️ User DB URL: jdbc:postgresql://localhost:5432/user_db
	•	🛢️ Product DB URL: jdbc:postgresql://localhost:5432/product_db
	•	👤 User: auction_app
	•	🔑 Password: auction123
	•	MongoDB
	•	🌐 URL: mongodb://auction_app:auction123@localhost:27017/authentication_db?authSource=admin
	•	👤 User: auction_app
	•	🔑 Password: auction123

## 🧩 Chapter 7: Microservices Patterns with Spring Cloud

### ⚠️ Alerts

- If you encounter issues accessing `http://localhost:8080/v1/api/auth`, please use  
`http://localhost:8072/authentication/v1/api/auth` instead.
The services are running behind the gateway, and the correct route is exposed through the gateway service.

- 🧭 **Service Startup Order Matters**  
  Run the services in the following order:
  1. 🧩 `service-discovery-services`
  2. 💪 `configuration-services`
  3. 🌐 `gateway-services`
  4. 📦 Other services like `authentication-services`, `user-services`, and `product-services`

- ⏱️ **Wait for Eureka**  
  After starting services, wait up to **30 seconds** before making any requests.  
  This ensures Eureka has synchronized its registry (due to default heartbeat/cache refresh intervals).

---

### 📁 Folder Structure

```
ch7/
├── 01-Service-Discovery/              # Introduces Eureka for service discovery
│   ├── service-discovery-services/    # Eureka Server
│   ├── authentication-services/       # Basic authentication service registered with Eureka
│   ├── user-services/                 # User service registered with Eureka
│   └── product-services/              # Product service registered with Eureka
├── 02-Load-Balancer/                  # Demonstrates load balancing with Spring Cloud LoadBalancer
│   ├── service-discovery-services/    # Eureka Server
│   ├── authentication-services/       # Authentication service with load balancing support
│   ├── user-services/                 # User service with load balancing support
│   └── product-services/              # Product service with load balancing support
├── 03-Gateway/                        # Introduces routing via Spring Cloud Gateway
│   ├── service-discovery-services/    # Eureka Server
│   ├── gateway-services/              # Spring Cloud Gateway routing requests
│   ├── authentication-services/       # Auth service behind the gateway
│   ├── user-services/                 # User service 
│   └── product-services/              # Product service
├── 04-Configuration-Server/           # Centralized configuration with Spring Cloud Config
│   ├── online-auction-configuration/  # Git-based configuration repository
│   ├── service-discovery-services/    # Eureka Server
│   ├── configuration-services/        # Spring Cloud Config Server
│   ├── gateway-services/              # Gateway consuming config from config server
│   ├── authentication-services/       # Auth service using centralized config
│   ├── user-services/                 # User service using centralized config
│   └── product-services/              # Product service using centralized config
├── 05-Resiliency/                     # Applies resilience patterns with Resilience4J
│   ├── service-discovery-services/    # Eureka Server
│   ├── configuration-services/        # Config Server
│   ├── gateway-services/              # Gateway 
│   ├── authentication-services/       # Auth service with esilience support such as circuit breaker and timeouts.
│   ├── user-services/                 # User service with resilience 
│   └── product-services/              # Product service
├── docker-resources/
│   ├── postgresql/
│   │   └── init.sql               # SQL DDL and DML scripts
│   ├── mongo-init/
│   │   └── init.js                # MongoDB: create DB, collections, insert data
│   ├── .env                       # PostgreSQL and MongoDB credentials
│   └── docker-compose.yml        # Spins up databases and populates data for IDE execution
└── postman/                           # Postman collection to test all services
    └── ch7.postman_collection.json
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9

---

### 🚀 Setup Instructions

#### 👨‍💻 Run Microservices via IDE

1. Navigate to the Docker folder: `ch7/docker-resources`
2. Start containers:
   ```bash
   docker-compose up -d
   ```
3. Open the microservices in your IDE  
   **Run them in this order:**
   - 🧩 Discovery Services
   - 💪 Configuration Services
   - 🌐 Gateway Services
4. Go to the desired chapter folder:
   - `01-Service-Discovery`
   - `02-Load-Balancer`
   - `03-Gateway`
   - `04-Configuration-Server`
   - `05-Resiliency`

For each service:
   ```bash
   mvn clean package
   mvn spring-boot:run
   ```
   To run multiple instances (e.g., for load balancing):
   ```bash
   mvn spring-boot:run -Dspring-boot.run.arguments="--server.port=<port_number>"
   ```
5. Import the Postman collection from the `postman` folder  
   📄 [Postman Import Documentation](https://learning.postman.com/docs/getting-started/importing-and-exporting/importing-data/)
6. Use Postman to send requests to your services

---

### 🔗 Database Connection Details

- **PostgreSQL**
  - 🛢️ User DB URL: `jdbc:postgresql://localhost:5432/user_db`
  - 🛢️ Product DB URL: `jdbc:postgresql://localhost:5432/product_db`
  - 👤 User: `auction_app`
  - 🔑 Password: `auction123`

- **MongoDB**
  - 🌐 URL: `mongodb://auction_app:auction123@localhost:27017/authentication_db?authSource=admin`
  - 👤 User: `auction_app`
  - 🔑 Password: `auction123`

## 🧩 Chapter 8: Event-Driven Architecture

### 📁 Folder Structure

```
ch8/
├── docker-resources/
│   ├── kafka/
│   │   └── docker-compose.yml         # Runs a Kafka instance
│   ├── databases/
│   │   ├── postgresql/
│   │   │   └── init.sql               # SQL DDL and DML scripts
│   │   ├── mongo-init/
│   │   │   └── init.js                # MongoDB: create DB, collections, insert data
│   │   ├── .env                       # PostgreSQL and MongoDB credentials
│   │   └── docker-compose.yml        # Runs PostgreSQL and MongoDB with populated data
├── postman/
│   └── ch08.postman_collection.json   # Postman collection for chapter 8 services
├── service-discovery-services/        # Eureka server for service discovery
├── configuration-services/            # Spring Cloud Config server
├── gateway-services/                  # Spring Cloud Gateway for routing
├── authentication-services/           # Authentication microservice
├── user-services/                     # User management microservice
├── product-services/                  # Product management microservice (optional)
├── auction-services/                  # Auction microservice
├── escrow-services/                   # Escrow microservice
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9

---

### 🚀 Setup Instructions

#### 👨‍💻 Run Microservices via IDE

1. Navigate to the databases folder:  ch8/docker-resources/databases
   ```bash
   docker-compose up -d
   ```

2. Navigate to the Kafka folder:  ch8/docker-resources/kafka
   ```bash
   docker-compose up -d
   ```

3. Open the microservices in your IDE from the `ch8` folder.

🧭 **Run the services in the following order**:
   - `service-discovery-services`
   - `configuration-services`
   - `gateway-services`
   - `authentication-services`
   - `user-services`
   - `auction-services`
   - `escrow-services`
   - `product-services` (optional)

4. Import the Postman collection from the `postman` folder:  
   📄 [Postman Import Documentation](https://learning.postman.com/docs/getting-started/importing-and-exporting/importing-data/)

5. Use Postman to test the services.

---

### 🔗 Database Connection Details

- **MongoDB**
  - 🌐 URL: `mongodb://auction_app:auction123@localhost:27017/authentication_db?authSource=admin`
  - 👤 User: `auction_app`
  - 🔑 Password: `auction123`

### 📡 Kafka Connection Details

- **Kafka**
  - 📡 Bootstrap Server: localhost:9092
  - 🔑 Security Type: Plaintext

## 🧩 Chapter 9: Pipe and Filter and Serverless Architecture

### 📁 Folder Structure

```
ch9/
├── docker-resources/
│   ├── postgresql/
│   │   └── init.sql               # SQL DDL and DML scripts
│   ├── .env                       # PostgreSQL credentials
│   └── docker-compose.yml        # Runs PostgreSQL and populates data
├── postman/
│   └── ch9.postman_collection.json  # Postman collection for chapter 9
├── data-files/                     # CSV files used for ETL batch processing
│   ├── Users.csv                   # Data for the user's table
│   ├── Products.csv                # Data for the product's table
│   ├── Bids.csv                    # Data for the bid's table
│   └── Auctions.csv                # Data for the auction's table
├── etl-batch-process/              # Batch processing code using Pipe and Filter architecture
└── alerting-faas/                  # Serverless code for sending Slack alerts
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9

---

### 🚀 Setup Instructions

#### 🛠️ Pipe and Filter Architecture

1. Navigate to the Docker folder: ch9/docker-resources
   ```bash
   docker-compose up -d
   ```
2. Open the `etl-batch-process` application in your IDE.
3. Build and run the application:
   ```bash
   mvn clean package
   mvn spring-boot:run
   ```
4. Use Postman to send requests defined in the chapter 9 collection.
5. Connect to PostgreSQL to verify inserted data:
   - 🛢️ URL: `jdbc:postgresql://localhost:5432/report_db`
   - 👤 User: `auction_app`
   - 🔑 Password: `auction123`

---

#### ☁️ Serverless Architecture

1. Open the `alerting-faas` application in your IDE.
2. Build and run the application:
   ```bash
   mvn clean package
   mvn spring-boot:run
   ```
3. Import the Postman collection from the `postman` folder.
4. Use Postman to send requests and test alerting behavior.

## 🔐 Chapter 10: Security

### ⚠️ Alerts
If you are facing issues when requesting http://localhost:8080/products, try to request http://127.0.0.1:8080/products

### 📁 Folder Structure

```
ch10/
├── docker-resources/
│   ├── postgresql/
│   │   └── init.sql               # SQL DDL and DML scripts
│   ├── mongo-init/
│   │   └── init.js                # MongoDB: create DB, collections, insert data
│   ├── .env                       # PostgreSQL and MongoDB credentials
│   └── docker-compose.yml        # Runs PostgreSQL and MongoDB with populated data
├── authorization-server/         # Spring Authorization Server to authenticate users and issue tokens
├── client-application/           # Application that authenticates via OAuth2 to access protected resources
└── product-services/             # Resource server that validates tokens and exposes secured endpoints
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9

---

### 🚀 Setup Instructions

#### 🛠️ Run Services via IDE

1. Navigate to the Docker folder: ch10/docker-resources
   ```bash
   docker-compose up -d
   ```

2. Open the services in your IDE from the `ch10` folder.
   - `authorization-server`
   - `product-services`
   - `client-application`

3. For each service execute:
   ```bash
   mvn clean package
   mvn spring-boot:run
   ```
---

### 🔗 Database Connection Details

- **MongoDB**
  - 🌐 URL: `mongodb://auction_app:auction123@localhost:27017/authentication_db?authSource=admin`
  - 👤 User: `auction_app`
  - 🔑 Password: `auction123`

## 📊 Chapter 11: Observability

### ⚠️ Alerts
Adding the `ObservationRegistry` to the `RestClient` is essential for enabling distributed tracing. It ensures that Spring propagates the trace context across microservices, resulting in connected and coherent traces in observability tools. The BeansConfiguration class was updated accordingly, as shown below.
```java
@LoadBalanced
@Bean
public RestClient.Builder restClient(CustomLoadBalancerInterceptor customLoadBalancerInterceptor, ObservationRegistry observationRegistry) {
    return RestClient
            .builder()
            .requestInterceptor(customLoadBalancerInterceptor)
            .observationRegistry(observationRegistry);
}
```

### 📁 Folder Structure

```
ch11/
├── docker-resources/
│   ├── databases/
│   │   ├── postgresql/
│   │   │   └── init.sql             # SQL DDL and DML scripts
│   │   ├── mongo-init/
│   │   │   └── init.js              # MongoDB: create DB, collections, insert data
│   │   ├── .env                     # PostgreSQL and MongoDB credentials
│   │   └── docker-compose.yml      # Runs PostgreSQL and MongoDB with populated data
│   ├── observability/
│   │   ├── docker-compose.yml      # Runs Elasticsearch, Logstash, Kibana, OpenTelemetry Collector, and Zipkin
│   │   ├── otel-collector-config.yml  # OpenTelemetry Collector configuration
│   │   └── logstash/
│   │       └── pipeline/
│   │           └── logstash.conf   # Logstash configuration for ingesting Spring Boot logs
├── postman/
│   └── ch11.postman_collection.json  # Postman collection for chapter 11
├── service-discovery-services/       # Eureka server
├── configuration-services/           # Spring Cloud Config server
├── gateway-services/                 # API gateway
├── authentication-services/          # Auth microservice
├── user-services/                    # User microservice
└── product-services/                 # Product microservice
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9

---

### 🚀 Setup Instructions

#### 🛠️ Run Services via IDE

1. Navigate to the databases folder: ch11/docker-resources/databases
   ```bash
   docker-compose up -d
   ```
2. Navigate to the observability folder: ch11/docker-resources/observability
   ```bash
   docker-compose up -d
   ```

3. Open the microservices in your IDE from the `ch11` folder.

### 🔗 Database Connection Details

- **MongoDB**
  - 🌐 URL: `mongodb://auction_app:auction123@localhost:27017/authentication_db?authSource=admin`
  - 👤 User: `auction_app`
  - 🔑 Password: `auction123`

## ✅ Chapter 12: Testing
### ⚠️ Alerts
The `user-services` and `auction-services` contain the tests presented in Chapter 12.

### 📁 Folder Structure

```
ch12/
├── docker-resources/
│   ├── databases/
│   │   ├── postgresql/
│   │   │   └── init.sql               # SQL DDL and DML scripts
│   │   ├── mongo-init/
│   │   │   └── init.js                # MongoDB: create DB, collections, insert data
│   │   ├── .env                       # PostgreSQL and MongoDB credentials
│   │   └── docker-compose.yml        # Runs PostgreSQL and MongoDB with populated data
│   ├── observability/
│   │   └── docker-compose.yml        # Runs Elasticsearch, Logstash, Kibana, OpenTelemetry Collector, and Zipkin
├── JMeter/
│   └── Thread Group.jmx              # JMeter configuration file for stress testing
├── postman/
│   └── ch12.postman_collection.json  # Postman collection for chapter 12
├── service-discovery-services/       # Eureka server
├── configuration-services/           # Spring Cloud Config server
├── gateway-services/                 # API gateway
├── authentication-services/          # Auth microservice
├── user-services/                    # User microservice (includes unit and integration tests)
├── product-services/                 # Product microservice
└── auction-services/                 # Presents the Unit tests using MOCK and SPY
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9  
- 🧪 [Apache JMeter 5.6.3](https://jmeter.apache.org/download_jmeter.cgi)

---

### 🚀 Instructions (for running stress tests)

#### ⚙️ Run Services via IDE

1. Navigate to the databases folder: ch12/docker-resources/databases
   ```bash
   docker-compose up -d
   ```

2. Navigate to the observability folder: ch12/docker-resources/observability
   ```bash
   docker-compose up -d
   ```

3. Open the microservices in your IDE from the `ch12` folder.

### 🔗 Database Connection Details

- **MongoDB**
  - 🌐 URL: `mongodb://auction_app:auction123@localhost:27017/authentication_db?authSource=admin`
  - 👤 User: `auction_app`
  - 🔑 Password: `auction123`

## ⚙️ Chapter 13: Performance and Optimizations

### 📁 Folder Structure

```
ch13/
├── docker-resources/
│   ├── databases/
│   │   ├── postgresql/
│   │   │   └── init.sql               # SQL DDL and DML scripts
│   │   ├── mongo-init/
│   │   │   └── init.js                # MongoDB: create DB, collections, insert data
│   │   ├── .env                       # PostgreSQL and MongoDB credentials
│   │   └── docker-compose.yml        # Runs PostgreSQL and MongoDB with populated data
│   ├── observability/
│   │   └── docker-compose.yml        # Runs Elasticsearch, Logstash, Kibana, OpenTelemetry Collector, and Zipkin
│   ├── redis/
│   │   └── docker-compose.yml        # Runs Redis
├── postman/
│   └── ch13.postman_collection.json  # Postman collection for chapter 13
├── 01-Local-Caching/                 # Demonstrates local in-memory caching 
│   └──product-services/              # Product microservice with local in-memory caching
├── 02-Distribuited-Caching/          # Demonstrates distributed caching with Redis
│   └──product-services/              # Product microservice with distributed caching with Redis
├── 03-Reactive-Programming/          # Showcases reactive programming with Spring WebFlux
│   └── authentication-services/      # Auth microservice
├── 04-Virtual-Threads/               # Demonstrates Java virtual threads (Project Loom) with Spring Boot
│   └── user-services/                # User microservice with Java virtual threads enabled.
├── configuration-services/           # Spring Cloud Config server
├── gateway-services/                 # Spring Cloud Gateway for API routing
├── postman/                          # Postman collection to test the services
└── service-discovery-services/       # Eureka server for service discovery
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9

---

### 🚀 Instructions (for running stress tests)

#### ⚙️ Run Services via IDE

1. Navigate to the databases folder: ch13/docker-resources/databases
   ```bash
   docker-compose up -d
   ```

2. Navigate to the observability folder: ch13/docker-resources/observability
   ```bash
   docker-compose up -d
   ```
3. Navigate to the redis folder: ch13/docker-resources/redis
   ```bash
   docker-compose up -d
   ```

4. Open the microservices in your IDE from the `ch13` folder.

🔁 **Run the services in the following order**:
   - `service-discovery-services`
   - `configuration-services`
   - `gateway-services`
   - `authentication-services`
   - `user-services`
   - `product-services`
   -   └── From `01-Local-Caching/` if you're focusing on **local in-memory caching** 
   -   └── From `02-Distribuited-Caching/` if you're focusing on **distributed caching with Redis**
4. For each service execute:
   ```bash
   mvn clean package
   mvn spring-boot:run
   ```
---

### 🔗 Database Connection Details

- **MongoDB**
  - 🌐 URL: `mongodb://auction_app:auction123@localhost:27017/authentication_db?authSource=admin`
  - 👤 User: `auction_app`
  - 🔑 Password: `auction123`

- **Redis**
  - 📍 Host: `127.0.0.1`
  - 🔌 Port: `6379`
  - 🔒 Authentication: *(not required by default)*

## 🧭 Chapter 14: Orchestration with Kubernetes

### 📁 Folder Structure

```
ch14/
├── docker-resources/                          # Local Docker setup for databases
│   ├── postgresql/
│   │   └── init.sql                           # SQL DDL and DML scripts
│   ├── mongo-init/
│   │   └── init.js                            # MongoDB: create DB, collections, and insert data
│   ├── .env                                   # Environment variables for DB credentials
│   └── docker-compose.yml                     # Starts PostgreSQL and MongoDB with populated data
├── postman/
│   └── ch14.postman_collection.json           # Postman collection for testing microservices
├── product-services/                          # Product microservice
├── authentication-services/                   # Authentication microservice
├── user-services/                             # User microservice
└── kubernetes/                                # Kubernetes manifests for service orchestration
    ├── databases/
    │   ├── mongodb-external-service.yaml      # Exposes MongoDB externally in the cluster
    │   └── postgresql-external-service.yaml   # Exposes PostgreSQL externally in the cluster
    ├── authentication/
    │   ├── authentication-services-deployment.yaml  # Deployment for authentication service
    │   ├── authentication-services-ingress.yaml     # Ingress configuration
    │   └── authentication-services-service.yaml     # Cluster service configuration
    ├── product/
    │   ├── product-services-deployment.yaml         # Deployment for product service
    │   ├── product-services-ingress.yaml            # Ingress configuration
    │   └── product-services-service.yaml            # Cluster service configuration
    └── user/
        ├── user-services-deployment.yaml            # Deployment for user service
        ├── user-services-ingress.yaml               # Ingress configuration
        └── user-services-service.yaml               # Cluster service configuration
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9  
- ☸️ Minikube
---

All deployment steps for the authentication service are thoroughly explained in the book.

### ⚠️ Attention 1

Some Kubernetes manifests under `ch14/kubernetes/` contain a hardcoded IP address (`192.168.100.89`) that must be replaced with your local machine’s actual IP address to ensure proper communication within the Minikube environment.

**Update the IP address in the following files:**

- `ch14/kubernetes/databases/mongodb-external-service.yaml`
- `ch14/kubernetes/databases/postgresql-external-service.yaml` (required if deploying the user and product services)
- `ch14/kubernetes/authentication/authentication-services-deployment.yaml`
- `ch14/kubernetes/user/user-services-deployment.yaml` (if deploying the user service)
- `ch14/kubernetes/product/product-services-deployment.yaml` (if deploying the product service)

To find your machine's IP address, run the following command:

```bash
ifconfig | grep "inet " | grep -v 127.0.0.1 | awk '{print $2}'
```

Replace every instance of `192.168.100.89` with the IP returned by this command. This step is critical for the services to connect to your local databases and function correctly within Minikube.

### ⚠️ Attention 2
The Kubernetes manifests for the product and user services are included in case you wish to deploy the complete application. Simply follow the same deployment steps outlined in the book for the authentication services, applying them to the product and user services.

## 🔁 Chapter 15: Continuous Integration and Continuous Deployment

### 📁 Folder Structure

```
ch15/
├── docker-resources/                                 # Local Docker setup for databases
│   ├── postgresql/
│   │   └── init.sql                                  # SQL DDL and DML scripts
│   ├── mongo-init/
│   │   └── init.js                                   # MongoDB: create DB, collections, and insert data
│   ├── .env                                          # Environment variables for DB credentials
│   └── docker-compose.yml                            # Starts PostgreSQL and MongoDB with populated data
├── postman/
│   └── ch15.postman_collection.json                  # Postman collection for testing microservices
├── authentication-services/                          # Authentication microservice
│   ├── kubernetes/                                   # Kubernetes manifests for service orchestration
│   │   ├── authentication-services-deployment.yaml   # Deployment for authentication service
│   │   ├── authentication-services-ingress.yaml      # Ingress configuration
│   │   └── authentication-services-service.yaml      # Cluster service configuration
|   └── Jenkinsfile                                   # Pipeline script for automating the build, test, Docker image push, and deployment to Minikube
├── product-services/                                # Product microservice
│   ├── kubernetes/                                  # Kubernetes manifests for service orchestration 
│   │   ├── product-services-deployment.yaml         # Deployment for product service
│   │   ├── product-services-ingress.yaml            # Ingress configuration
│   │   └── product-services-service.yaml            # Cluster service configuration
|   └── Jenkinsfile                                  # Pipeline script for automating the build, test, Docker image push, and deployment to Minikube
└── user-services/                                   # User microservice
   ├── kubernetes/                                  # Kubernetes manifests for service orchestration 
   │   ├── user-services-deployment.yaml            # Deployment for user service
   │   ├── user-services-ingress.yaml               # Ingress configuration
   │   └── user-services-service.yaml               # Cluster service configuration
   └── Jenkinsfile                                  # Pipeline script for automating the build, test, Docker image push, and deployment to Minikube
```

---

### ⚙️ Prerequisites

- ☕ Java 21  
- 🐳 Docker & Docker Compose  
- 🧰 Maven 3.9.9  
- ☸️ Minikube
- 🌐 ngrok
- 🐙 GitHub account
- 🤖 Jenkins
---

### ⚠️ Attention 1
The Kubernetes manifests must be located in the project’s root directory, as Jenkins depends on this structure to deploy services to Minikube.
In the **Setting up GitHub** section of Chapter 15, before pushing the project to your GitHub repository, navigate to ```authentication-services/kubernetes```, open the ```authentication-services-deployment.yaml``` file and replace the hardcoded IP 192.168.100.89 with your local machine’s IP address, which you can retrieve using the following command:
```bash
    ifconfig | grep "inet " | grep -v 127.0.0.1 | awk '{print $2}' 
   ```
This command will return your active IP address, which must be used in the deployment configuration to ensure proper communication within the Minikube environment.

### ⚠️ Attention 2
The configured Jenkinsfile and Kubernetes manifests for the product and user services are included in case you wish to deploy the complete application. Simply follow the same deployment steps outlined in the book for the authorization server, applying them to the product and user services.

### ⚠️ Attention 3
Windows developers may have problems with their Windows anti-virus when downloading nGrok. Please install nGrok via Chocolatey.

### Installing Chocolatey

1. **Open PowerShell as Administrator**  
   - Press `Windows + X` and select **Terminal (Admin)** or **PowerShell (Admin)**.

2. **Run the following command**:
   ```powershell
   Set-ExecutionPolicy Bypass -Scope Process -Force; `
   [System.Net.ServicePointManager]::SecurityProtocol = 3072; `
   iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
   ```

3. **Verify installation**:
   ```powershell
      choco -? 
   ```
4. **Follow the steps described on the Ngrok webpage to install ngrok at: https://ngrok.com/downloads/windows**

### 👨‍💼 Who This Book is For
This book is for Java engineers transitioning to software architecture roles and architects seeking deeper insight into Spring-based architectural styles. Mid-level Spring Boot developers will be able to master architecture principles to build scalable, maintainable applications with the help of practical guidance on using modern architectural patterns.

## 💬 Feedback and Contributions

Your feedback is invaluable! Feel free to contact us about issues, suggest improvements, or share your thoughts. This repository will be updated with any errata and additional resources to accompany the book.

## 👤 About the Author
Wanderson Xesquevixos is a seasoned software engineer and architect with over twenty-five years of experience. He has dedicated his career to developing and designing complex systems for many global companies in the banking, telecom, tourism, retail, and e-commerce industries. He earned his computer science degree from UNIVAP in 2005. He holds an MBA in Data Science and Analytics and is pursuing another MBA in Software Engineering from the prestigious Universidade de São Paulo (USP). He holds certifications as a Java Programmer, Web Component Developer, JEE Business Component Developer, and AWS Certified Solutions Architect. Originally from Jacareí, SP, Wanderson resides in São Francisco do Sul, SC, with his wife Caroline and son Alexander.
<div align="center"><img src="me.png" alt="Software Architecture with Spring" width="50%"/></div>

*🚀 Thank you for embarking on this journey in software architecture! Happy coding and architecting!*

Software-Architecture-with-Spring

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README