Spring Boot library reference

A map of the Maven ecosystem this skill set assumes, organized by domain rather than alphabetically, so a task ("I need caching", "I need to call another service resiliently") points straight at the relevant table. Load the matching reference file below rather than trying to hold all domains in context at once.

How to use this reference

1. Spring Boot-managed dependencies first. Anything with a spring-boot-starter-* coordinate, or anything in Spring Boot's own dependency-management BOM (Jackson, SLF4J/Logback, JDBC drivers, Testcontainers modules pulled in via spring-boot-testcontainers, etc.), should be declared without a version — let the parent POM / BOM pin it. Hand-pinning a version Spring Boot already manages is how a project ends up with two conflicting versions of the same transitive dependency.
2. Non-Boot-managed libraries need an explicit version (Resilience4j, MapStruct, Lombok, jjwt, Bucket4j, etc.) — check the reference tables below for a recent one, but treat every version number here as a snapshot at the time this skill was written, not a live source of truth. Verify against Maven Central / the library's own release page before pinning it in a real project — these ecosystems move fast enough that a hardcoded version here will eventually be stale.
3. One skill per domain already exists for the "how", this skill is the "what". This file tells you which artifact to reach for; spring-boot-jpa/spring-boot-mongodb/spring-boot-jdbc (persistence), spring-boot-security, spring-boot-microservices (resilience/messaging), spring-boot-observability, and spring-boot-test cover how to actually use what you picked.

Domain index