138건 · 관련도순
Use when versioning Spring MVC or WebFlux APIs in Spring Boot 3 / Spring Framework 6. Covers explicit URL, header, and media-type strategies, compatibility rules, and deprecation handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding Spring AI-specific model observations, token usage, latency, externally configured cost attribution, advisor telemetry, or protected prompt and completion logging. Use production-observability for general service metrics, health, logs, and OTLP setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when generating or refactoring Spring Boot 4 JPA entities, repositories, queries, projections, persistence tests, entity relationships, embeddables, IDs, or Hibernate mappings. Covers Jakarta Persistence 3.2 imports, Hibernate 7 entity modeling, new-state detection, N+1 prevention, projections, keyset pagination, batch writes, and common agent mistakes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating database migrations, schema changes, seed data, or any SQL that modifies database structure. Covers Flyway naming conventions, versioning, and safe migration patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building batch jobs, ETL pipelines, scheduled imports/exports, or any chunk-oriented bulk processing with Spring Batch. Covers the Spring Batch 6 / Boot 4 builder API, resourceless vs JDBC job repositories, restartability and idempotent job parameters, reader/writer thread-safety, fault tolerance, and chunk transaction boundaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when integrating LLMs, chat clients, embeddings, RAG pipelines, or AI agents into Spring Boot. Covers Spring AI 2.0 ChatClient, prompt templates, embeddings, vector stores, and structured output. Use when user mentions Spring AI, LLM, ChatGPT, Claude, RAG, embeddings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding retries, backoff, or concurrency limits to Spring Boot 4 / Spring Framework 7 code with core Retryable and ConcurrencyLimit support. Covers enablement, backoff, proxy limits, and behavior after retries are exhausted.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding service-wide Spring Boot 4 Actuator, Micrometer Observation and Tracing, OpenTelemetry or OTLP export, structured logging, health probes, dashboards, or alerts. Combine with ai-observability only for Spring AI-specific token, prompt, and model telemetry.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing exception mapping or RFC 9457 error responses in Spring Boot 4. Preserve an existing legacy error contract unless migration is requested.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when annotating nullability in Spring Boot 4 / Spring Framework 7, migrating to JSpecify, integrating Kotlin, or enabling build-time null checks with NullAway.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing tenant resolution, database or schema isolation, Hibernate 7 tenancy, reactive tenant context, migrations, caches, jobs, or authorization in Spring Boot 4.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working in a multi-module Maven project. Covers parent POM conventions, shared dependency management, inter-module rules, build ordering, and Spring Boot 4 modular starter selection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when exposing Spring Boot 4 application capabilities through Model Context Protocol tools, resources, or prompts. Covers Spring AI 2.0 MCP annotations, transport selection, schemas, errors, security, and the standalone MCP Java SDK 2.x.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when calling external HTTP APIs from Spring Boot 4 / Spring Framework 7 with declarative HttpExchange interfaces. Covers ImportHttpServices, grouped base URLs and timeouts, and RestClient versus WebClient selection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4. Covers modular starters, event contracts, idempotency, retries, dead letters, and outbox delivery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when evolving aggregate invariants, value objects or domain events in an existing DDD-style Spring Boot 4 application, or when DDD is explicitly requested. Preserve existing API identifiers and architecture when changing domain behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building Spring Cloud Gateway 5 on Spring Boot 4, including WebFlux or Web MVC routes, edge authentication, trusted headers, rate limits, timeouts, and resilience. Do not use for ordinary outbound HTTP clients or domain orchestration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when packaging Spring Boot 4 as an OCI image, JVM container, AOT application, or GraalVM native executable. Covers buildpacks, layers, runtime hints, probes, security, and verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when versioning Spring MVC or WebFlux APIs in Spring Boot 4 / Spring Framework 7. Covers built-in mapping versions, request version resolution, defaults, supported versions, and deprecation headers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the complete Spring Boot 3 request path is reactive: WebFlux controllers, Reactor pipelines, R2DBC persistence, streaming, backpressure, or cancellation. For defining and registering declarative outbound API interfaces, use http-interface-clients.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when defining or debugging Spring Boot 3 database transaction boundaries, rollback, propagation, optimistic-lock retries, or commit-bound events. For duplicate HTTP commands use idempotency-patterns; for reactive transactions use webflux-reactive-patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing tests of any kind — unit, slice, or integration. Covers test structure, naming conventions, Mockito patterns, @WebMvcTest, @DataJpaTest, and Testcontainers setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an application issues and validates its own first-party JWT access and refresh tokens, including authentication filters, password encoding, RBAC, and method security. For JWTs issued by Keycloak, Auth0, Okta, Cognito, or another authorization server, use oauth2-resource-server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when organizing or verifying a modular Spring Boot monolith with Spring Modulith, including module APIs, dependency rules and reliable module events. Do not restructure an application into modules for an unrelated endpoint change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.