spring-boot-microserviceslisted

# Spring Boot Microservices A practitioner's skill for building and reviewing **production-grade** Spring Boot microservices the way strong teams do it in 2026. Three jobs — pick the one the request needs: - **Design** — boundaries, API contracts, data ownership, communication style. - **Scaffold / build** — generate a correct modern project; implement features well. - **Review / audit** — judge an existing service against modern standards. Most requests blend these. This file is the router; **it stays loaded, so it's kept lean on purpose.** Depth lives in `references/` — load a reference only when the task actually reaches that topic, and see the [reference map](#reference-map) at the bottom. ## Orient, and match effort to the task Before acting, settle three things — getting them wrong is the top cause of correct- but-useless advice: **(1) which mode** (ask if genuinely ambiguous); **(2) the version generation** — check `pom.xml`/`build.gradle` and the JDK, never assume (see [Version policy](#version-policy)); **(3) architecture context** — greenfield, one service in an existing estate, or a modular monolith. For existing code, actually read the build file, main class, a representative controller/service/repository, and `application.yml` before forming an opinion. Then calibrate how hard to lean on this skill — this matters because a capable model already writes correct idiomatic Spring Boot (adding `@Valid`, returning a 404, wiring a `SecurityFilterChain`) and loadin