Spring Boot Performance and Resilience

When to use

Invoke when a Spring Boot service must hit a stated latency, throughput, or availability target and the SLOs, dependency criticality, degradation behavior, and retry/timeout budgets have been decided by performance, reliability, and backend-architecture. Use it for new services entering load, for hardening an existing service before scale-up, or for review when production is page-prone, slow, or failing under partial outages.

Do not use for picking SLOs (use reliability), for capacity modelling or scaling strategy across components (use performance), for designing service boundaries or async contracts (use backend-architecture), for choosing the cache substrate or queue (use data-architecture or backend-architecture), for cluster-level autoscaling, PDBs, or HPA (use infrastructure-platform and implementations/infrastructure/kubernetes), or for image-level JVM packaging (use implementations/infrastructure/kubernetes/dockerfile-and-jvm-tuning).

Inputs

Required:

• Spring Boot service source tree (or scaffold output).
• Approved per-path SLOs from reliability (availability and latency targets, error budget, evaluation window).
• Approved backend-architecture.md declaring synchronous and asynchronous dependencies, idempotency and retry semantics per call, and degradation behavior per journey.
• Container memory and CPU limits the service will run under, or the assumption that those land via deployment configuration.

Optional: