java-spring-enterprise

What problem does it solve?

Enterprises building backend systems often struggle to structure Spring Boot applications for maintainability, testability, and production reliability across transactions, database pooling, and observability concerns. This Skill provides clear architecture patterns, transaction guidance, connection pool tuning, and observability best practices to avoid common anti-patterns like fat controllers, leaking domain entities, incorrect transactional scopes, and misconfigured connection pools.

Core Features & Use Cases

• Architecture Guidance: Clean / Hexagonal project layout with domain, application, and adapter separation to enforce framework-agnostic domain logic.
• Transactional Best Practices: Rules for @Transactional usage including readOnly reads, explicit isolation on financial operations, and avoiding class-level transactional blast radii.
• Performance & Infrastructure: HikariCP tuning recommendations, Virtual Threads guidance for I/O-bound workloads, and Micrometer/OpenTelemetry observability setup.
• Use Case: Scaffold a new orders service that maps controllers to use cases, keeps domain free of Spring, configures HikariCP pool size, and records custom Micrometer metrics and traces.

Quick Start

Scaffold a new Spring Boot project using hexagonal layers, configure HikariCP pool-sizing, enable Micrometer and OpenTelemetry, and implement a CreateOrder use case where controllers delegate to application use cases and the domain remains framework-agnostic.