Spring Cloud Microservices Revised Edition – Intro and New Tech Stack
After finishing the Spring Boot source‑code series, the author launches a refreshed Spring Cloud microservices tutorial built on Spring Boot 3.x, Jakarta EE, GraalVM native images, full production‑grade demos, Kubernetes deployment, observability and performance testing, outlining a 12‑episode roadmap.
Why rewrite?
Spring Boot 2.7.x and Spring Cloud 2021.x used in the original series are now outdated. The mainstream ecosystem has moved to Spring Boot 3.x, which includes Jakarta EE namespace changes, GraalVM native‑image support, and new observability APIs. The original demos lacked production‑grade examples, covered only Docker deployment, and scattered code forced readers to copy snippets from blog posts.
New technical stack (Spring Cloud Microservices Reboot)
Framework layer : Spring Boot 3.2.x (or 3.3.x), Spring Cloud 2023.x, Java 17/21
Service governance : Nacos 2.3.x (service registration & configuration), Spring Cloud Gateway 4.x, OpenFeign 4.x, built‑in LoadBalancer (replaces Ribbon)
Fault tolerance : Sentinel 1.8.6
Tracing : SkyWalking 9.x
Distributed transactions : Seata 1.7.x (AT and TCC modes)
Deployment : Docker + Docker Compose, Kubernetes 1.28+ (YAML manifests), Helm Charts
Observability : Micrometer + Prometheus, Grafana dashboards, Loki log aggregation
Series plan (12 episodes)
Intro and architecture design – comparison of old vs. new versions and technology‑selection rationale
Nacos service registration & discovery – compatibility, multi‑environment isolation (namespace + group)
OpenFeign service calls – HTTP client changes and usage patterns
Spring Cloud Gateway – WebFlux changes, unified JWT authentication
Nacos configuration center – dynamic refresh, encrypted configurations
Sentinel fault tolerance – rate limiting, circuit breaking, persistence, production tuning
SkyWalking tracing – new probes, alert configuration
Seata distributed transactions – AT vs. TCC comparison, performance optimization
Micrometer observability – metric collection, Grafana panels
Docker Compose full deployment – one‑click start of all services
Kubernetes production deployment – Deployment, Service, Ingress, HPA
Performance testing & tuning – JMeter scripts, full post‑mortem analysis
Project repository
Repository URL: https://github.com/chenranyi/spring-cloud-reboot.git Directory layout (representative):
spring-cloud-microservice-reboot/
├── parent/ # parent pom for unified version management
├── common/ # shared utilities
├── user-service/ # user domain service
├── article-service/ # article domain service
├── comment-service/ # comment domain service
├── gateway/ # API gateway
├── docker-compose/ # Docker Compose files
├── k8s/ # Kubernetes manifests
│ ├── namespace.yaml
│ ├── configmap.yaml
│ ├── deployments/
│ ├── services/
│ └── ingresses/
├── helm-charts/ # Helm chart definitions
├── monitoring/ # Prometheus, Grafana, Loki configs
│ ├── prometheus.yml
│ └── grafana-dashboards/
└── scripts/ # helper scripts (e.g., docker-build.sh)Each episode is tagged in the repository (e.g., reboot-ep01, reboot-ep02, … reboot-ep12).
Comparison with the original edition
Spring Boot : 2.7.x → 3.2.x/3.3.x
Spring Cloud : 2021.x → 2023.x
Java version : 8/11 → 17/21
Jakarta EE namespace : javax.* → jakarta.* Project organization : scattered code → unified multi‑module repository
Production examples : minimal demos → complete runnable projects for each component
Kubernetes deployment : simple examples → full YAML manifests + Helm charts
Observability : none → Prometheus + Grafana + Loki integration
Performance testing : absent → full JMeter scripts with analysis
GraalVM native image : not covered → step‑by‑step native‑image build guide using Spring Boot 3.x
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Coder Trainee
Experienced in Java and Python, we share and learn together. For submissions or collaborations, DM us.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
