Source profileQuality 76/100

affaan-m/ECC/docs/es/skills/springboot-patterns/SKILL.md

springboot-patterns

Patrones de arquitectura Spring Boot, diseño de API REST, servicios en capas, acceso a datos, caché, procesamiento asíncrono y logging. Usar para trabajo de backend en Java con Spring Boot.

Source repository stars
234,327
Declared platforms
0
Static risk flags
0
Last source update
2026-07-27
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Patrones de arquitectura y API de Spring Boot para servicios escalables y listos para producción.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/affaan-m/ECC --skill "docs/es/skills/springboot-patterns"
    Safe inspection promptEditorial

    Inspect the Agent Skill "springboot-patterns" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/docs/es/skills/springboot-patterns/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Cuándo Activar

      Construir APIs REST con Spring MVC o WebFlux

      Construir APIs REST con Spring MVC o WebFluxEstructurar capas controller → service → repositoryConfigurar Spring Data JPA, caché o procesamiento asíncrono
    2. 02

      Estructura de API REST

      Review the “Estructura de API REST” section in the pinned source before continuing.

      Review and apply the “Estructura de API REST” source section.
    3. 03

      Patrón de Repositorio (Spring Data JPA)

      Review the “Patrón de Repositorio (Spring Data JPA)” section in the pinned source before continuing.

      Review and apply the “Patrón de Repositorio (Spring Data JPA)” source section.
    4. 04

      Capa de Servicio con Transacciones

      Review the “Capa de Servicio con Transacciones” section in the pinned source before continuing.

      Review and apply the “Capa de Servicio con Transacciones” source section.
    5. 05

      DTOs y Validación

      Review the “DTOs y Validación” section in the pinned source before continuing.

      Review and apply the “DTOs y Validación” source section.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score76/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars234,327SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    affaan-m/ECC
    Skill path
    docs/es/skills/springboot-patterns/SKILL.md
    Commit
    4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Patrones de Desarrollo Spring Boot

    Patrones de arquitectura y API de Spring Boot para servicios escalables y listos para producción.

    Cuándo Activar

    • Construir APIs REST con Spring MVC o WebFlux
    • Estructurar capas controller → service → repository
    • Configurar Spring Data JPA, caché o procesamiento asíncrono
    • Agregar validación, manejo de excepciones o paginación
    • Configurar perfiles para entornos dev/staging/producción
    • Implementar patrones orientados a eventos con Spring Events o Kafka

    Estructura de API REST

    @RestController
    @RequestMapping("/api/markets")
    @Validated
    class MarketController {
      private final MarketService marketService;
    
      MarketController(MarketService marketService) {
        this.marketService = marketService;
      }
    
      @GetMapping
      ResponseEntity<Page<MarketResponse>> list(
          @RequestParam(defaultValue = "0") int page,
          @RequestParam(defaultValue = "20") int size) {
        Page<Market> markets = marketService.list(PageRequest.of(page, size));
        return ResponseEntity.ok(markets.map(MarketResponse::from));
      }
    
      @PostMapping
      ResponseEntity<MarketResponse> create(@Valid @RequestBody CreateMarketRequest request) {
        Market market = marketService.create(request);
        return ResponseEntity.status(HttpStatus.CREATED).body(MarketResponse.from(market));
      }
    }
    

    Patrón de Repositorio (Spring Data JPA)

    public interface MarketRepository extends JpaRepository<MarketEntity, Long> {
      @Query("select m from MarketEntity m where m.status = :status order by m.volume desc")
      List<MarketEntity> findActive(@Param("status") MarketStatus status, Pageable pageable);
    }
    

    Capa de Servicio con Transacciones

    @Service
    public class MarketService {
      private final MarketRepository repo;
    
      public MarketService(MarketRepository repo) {
        this.repo = repo;
      }
    
      @Transactional
      public Market create(CreateMarketRequest request) {
        MarketEntity entity = MarketEntity.from(request);
        MarketEntity saved = repo.save(entity);
        return Market.from(saved);
      }
    }
    

    DTOs y Validación

    public record CreateMarketRequest(
        @NotBlank @Size(max = 200) String name,
        @NotBlank @Size(max = 2000) String description,
        @NotNull @FutureOrPresent Instant endDate,
        @NotEmpty List<@NotBlank String> categories) {}
    
    public record MarketResponse(Long id, String name, MarketStatus status) {
      static MarketResponse from(Market market) {
        return new MarketResponse(market.id(), market.name(), market.status());
      }
    }
    

    Manejo de Excepciones

    @ControllerAdvice
    class GlobalExceptionHandler {
      @ExceptionHandler(MethodArgumentNotValidException.class)
      ResponseEntity<ApiError> handleValidation(MethodArgumentNotValidException ex) {
        String message = ex.getBindingResult().getFieldErrors().stream()
            .map(e -> e.getField() + ": " + e.getDefaultMessage())
            .collect(Collectors.joining(", "));
        return ResponseEntity.badRequest().body(ApiError.validation(message));
      }
    
      @ExceptionHandler(AccessDeniedException.class)
      ResponseEntity<ApiError> handleAccessDenied() {
        return ResponseEntity.status(HttpStatus.FORBIDDEN).body(ApiError.of("Forbidden"));
      }
    
      @ExceptionHandler(Exception.class)
      ResponseEntity<ApiError> handleGeneric(Exception ex) {
        // Registrar errores inesperados con stack traces
        return ResponseEntity.status(HttpStatus.INTERNAL_SERVER_ERROR)
            .body(ApiError.of("Internal server error"));
      }
    }
    

    Caché

    Requiere @EnableCaching en una clase de configuración.

    @Service
    public class MarketCacheService {
      private final MarketRepository repo;
    
      public MarketCacheService(MarketRepository repo) {
        this.repo = repo;
      }
    
      @Cacheable(value = "market", key = "#id")
      public Market getById(Long id) {
        return repo.findById(id)
            .map(Market::from)
            .orElseThrow(() -> new EntityNotFoundException("Market not found"));
      }
    
      @CacheEvict(value = "market", key = "#id")
      public void evict(Long id) {}
    }
    

    Procesamiento Asíncrono

    Requiere @EnableAsync en una clase de configuración.

    @Service
    public class NotificationService {
      @Async
      public CompletableFuture<Void> sendAsync(Notification notification) {
        // enviar email/SMS
        return CompletableFuture.completedFuture(null);
      }
    }
    

    Logging (SLF4J)

    @Service
    public class ReportService {
      private static final Logger log = LoggerFactory.getLogger(ReportService.class);
    
      public Report generate(Long marketId) {
        log.info("generate_report marketId={}", marketId);
        try {
          // lógica
        } catch (Exception ex) {
          log.error("generate_report_failed marketId={}", marketId, ex);
          throw ex;
        }
        return new Report();
      }
    }
    

    Middleware / Filtros

    @Component
    public class RequestLoggingFilter extends OncePerRequestFilter {
      private static final Logger log = LoggerFactory.getLogger(RequestLoggingFilter.class);
    
      @Override
      protected void doFilterInternal(HttpServletRequest request, HttpServletResponse response,
          FilterChain filterChain) throws ServletException, IOException {
        long start = System.currentTimeMillis();
        try {
          filterChain.doFilter(request, response);
        } finally {
          long duration = System.currentTimeMillis() - start;
          log.info("req method={} uri={} status={} durationMs={}",
              request.getMethod(), request.getRequestURI(), response.getStatus(), duration);
        }
      }
    }
    

    Paginación y Ordenamiento

    PageRequest page = PageRequest.of(pageNumber, pageSize, Sort.by("createdAt").descending());
    Page<Market> results = marketService.list(page);
    

    Llamadas Externas Resilientes a Errores

    public <T> T withRetry(Supplier<T> supplier, int maxRetries) {
      int attempts = 0;
      while (true) {
        try {
          return supplier.get();
        } catch (Exception ex) {
          attempts++;
          if (attempts >= maxRetries) {
            throw ex;
          }
          try {
            Thread.sleep((long) Math.pow(2, attempts) * 100L);
          } catch (InterruptedException ie) {
            Thread.currentThread().interrupt();
            throw ex;
          }
        }
      }
    }
    

    Limitación de Velocidad (Filtro + Bucket4j)

    Nota de Seguridad: La cabecera X-Forwarded-For no es confiable por defecto porque los clientes pueden falsificarla. Solo usar cabeceras reenviadas cuando:

    1. La aplicación está detrás de un proxy inverso de confianza (nginx, AWS ALB, etc.)
    2. Se ha registrado ForwardedHeaderFilter como un bean
    3. Se ha configurado server.forward-headers-strategy=NATIVE o FRAMEWORK en las propiedades de la aplicación
    4. El proxy está configurado para sobrescribir (no agregar) la cabecera X-Forwarded-For

    Cuando ForwardedHeaderFilter está correctamente configurado, request.getRemoteAddr() retornará automáticamente la IP correcta del cliente desde las cabeceras reenviadas. Sin esta configuración, usar request.getRemoteAddr() directamente — retorna la IP de la conexión inmediata, que es el único valor confiable.

    @Component
    public class RateLimitFilter extends OncePerRequestFilter {
      private final Map<String, Bucket> buckets = new ConcurrentHashMap<>();
    
      /*
       * SEGURIDAD: Este filtro usa request.getRemoteAddr() para identificar clientes en la limitación
       * de velocidad.
       *
       * Si la aplicación está detrás de un proxy inverso (nginx, AWS ALB, etc.), se DEBE configurar
       * Spring para manejar correctamente las cabeceras reenviadas:
       *
       * 1. Establecer server.forward-headers-strategy=NATIVE (para plataformas cloud) o FRAMEWORK
       *    en application.properties/yaml
       * 2. Si se usa la estrategia FRAMEWORK, registrar ForwardedHeaderFilter:
       *
       *    @Bean
       *    ForwardedHeaderFilter forwardedHeaderFilter() {
       *        return new ForwardedHeaderFilter();
       *    }
       *
       * 3. Asegurar que el proxy sobrescriba (no agregue) la cabecera X-Forwarded-For para prevenir
       *    falsificación
       * 4. Configurar server.tomcat.remoteip.trusted-proxies o equivalente para el contenedor
       *
       * Sin esta configuración, request.getRemoteAddr() retorna la IP del proxy, no del cliente.
       * NO leer X-Forwarded-For directamente — es trivialmente falsificable sin manejo de proxy confiable.
       */
      @Override
      protected void doFilterInternal(HttpServletRequest request, HttpServletResponse response,
          FilterChain filterChain) throws ServletException, IOException {
        String clientIp = request.getRemoteAddr();
    
        Bucket bucket = buckets.computeIfAbsent(clientIp,
            k -> Bucket.builder()
                .addLimit(Bandwidth.classic(100, Refill.greedy(100, Duration.ofMinutes(1))))
                .build());
    
        if (bucket.tryConsume(1)) {
          filterChain.doFilter(request, response);
        } else {
          response.setStatus(HttpStatus.TOO_MANY_REQUESTS.value());
        }
      }
    }
    

    Jobs en Segundo Plano

    Usar @Scheduled de Spring o integrar con colas (Kafka, SQS, RabbitMQ). Mantener los handlers idempotentes y observables.

    Observabilidad

    • Logging estructurado (JSON) mediante Logback encoder
    • Métricas: Micrometer + Prometheus/OTel
    • Trazado: Micrometer Tracing con backend OpenTelemetry o Brave

    Configuraciones para Producción

    • Preferir inyección por constructor, evitar inyección por campo
    • Habilitar spring.mvc.problemdetails.enabled=true para errores RFC 7807 (Spring Boot 3+)
    • Configurar tamaños del pool HikariCP para la carga de trabajo, establecer timeouts
    • Usar @Transactional(readOnly = true) para consultas
    • Reforzar null-safety mediante @NonNull y Optional donde corresponda

    Recuerda: Mantener los controllers delgados, los servicios enfocados, los repositorios simples y los errores manejados centralmente. Optimizar para mantenibilidad y testabilidad.

    Alternatives

    Compare before choosing