Microservices in Spring Boot: Architecture, Design Patterns, and Production Practices

Introduction

Building microservices is easy. Building production-ready microservices that scale, handle network partitions, and maintain consistency is incredibly difficult.

When transitioning from a monolith to microservices, we trade simple in-memory function calls for unpredictable network hops. In this guide, we map the essential components of a Spring Boot microservices ecosystem, focusing on architectural resiliency, load balancing, and container orchestration.

♦ ♦ ♦

1. System Architecture Blueprint

In a production microservices topology, core business microservices (e.g., Order Service, Catalog Service) are supported by dynamic discovery, configuration, and routing layers.

Core Infrastructure Services:

Spring Cloud Gateway: The entry point. It manages path-based routing, intercepts authentication (JWT decoding), rate limits clients, and handles CORS headers.
Eureka Service Registry: Coordinates network locations. Microservices register their dynamic IP addresses and ports with Eureka, and Feign/LoadBalancer queries Eureka for routing lookups.
Spring Cloud Config Server: Centralized configuration store. Externalizes environment settings by pulling YAML files directly from a private Git repository or HashiCorp Vault.
Resilience4j: Implements circuit breakers and rate limiters to prevent cascading system failures.

1resilience4j.circuitbreaker: 2 instances: 3 inventoryBreaker: 4 registerHealthIndicator: true 5 slidingWindowSize: 10 6 minimumNumberOfCalls: 5 7 failureRateThreshold: 50 8 waitDurationInOpenState: 10000ms 9 permittedNumberOfCallsInHalfOpenState: 3 10`` 11 12> [!TIP] 13> Always configure separate fallback methods depending on the type of Exception. For instance, throw an immediate 404 for `EntityNotFoundException`, but trigger the fallback behavior for `ConnectException` or `TimeoutException`. 14 15--- 16 17## 3. Local Orchestration with Docker Compose 18 19To run a microservices ecosystem locally for development, we containerize our build artifacts and use Docker Compose to spin up the architecture. 20 21Here is a sample `docker-compose.yml` coordinating the config server, discovery registry, and database dependency: 22 23```yaml 24version: '3.8' 25 26services: 27 eureka-server: 28 image: my-registry/eureka-server:latest 29 ports: 30 - "8761:8761" 31 networks: 32 - portfolio-network 33 34 config-server: 35 image: my-registry/config-server:latest 36 ports: 37 - "8888:8888" 38 environment: 39 - SPRING_PROFILES_ACTIVE=git 40 - SPRING_CLOUD_CONFIG_SERVER_GIT_URI=https://github.com/my-org/config-repo 41 networks: 42 - portfolio-network 43 44 mysql-db: 45 image: mysql:8.0 46 environment: 47 MYSQL_ROOT_PASSWORD=root 48 MYSQL_DATABASE=orders_db 49 ports: 50 - "3306:3306" 51 networks: 52 - portfolio-network 53 54 order-service: 55 image: my-registry/order-service:latest 56 ports: 57 - "8081:8081" 58 environment: 59 - SPRING_DATASOURCE_URL=jdbc:mysql://mysql-db:3306/orders_db 60 - EUREKA_CLIENT_SERVICEURL_DEFAULTZONE=http://eureka-server:8761/eureka/ 61 - SPRING_CONFIG_IMPORT=configserver:http://config-server:8888 62 depends_on: 63 - eureka-server 64 - config-server 65 - mysql-db 66 networks: 67 - portfolio-network 68 69networks: 70 portfolio-network: 71 driver: bridge

Microservices in Spring Boot: Architecture, Design Patterns, and Production Practices

Introduction

1. System Architecture Blueprint

Core Infrastructure Services:

Enjoyed this article?

2. Implementing Circuit Breakers with Resilience4j

Maven Configuration

Java Code Annotation

Config properties (`application.yml`)

Conclusion

Introduction

1. System Architecture Blueprint

Core Infrastructure Services:

Enjoyed this article?

2. Implementing Circuit Breakers with Resilience4j

Maven Configuration

Java Code Annotation

Config properties (application.yml)

Conclusion

Config properties (`application.yml`)