java-coding-standards

Topics in the source

• Java Coding Standards
• When to Use
• How It Works
• Framework Detection
• Core Principles
• Examples
• Naming
• Immutability

Standards for readable, maintainable Java (17+) code in Spring Boot and Quarkus services. Writing or reviewing Java code in Spring Boot or Quarkus projects Enforcing naming, immutability, or exception handling conventions Working with records, sealed classes, or pattern matching (Java 17+) Reviewing use of Optional, streams, or generics Structuring packages and project layout [QUARKUS]: Working with CDI scopes, Panache entities, or reactive pipelines Before applying standards, determine the framework from the build file: Build file contains quarkus → apply [QUARKUS] conventions Build file contains spring-boot → apply [SPRING] conventions Neither detected → apply shared conventions only Prefer clarity over cleverness Immutable by default; minimize shared mutable state Fail fast with meaningful exceptions Consistent naming and package structure [QUARKUS]: Favor build-time over runtime processing; avoid runtime reflection where possible The sections below show concrete Spring Boot, Quarkus, and shared Java examples for naming, immutability, dependency injection, reactive code, exceptions, project layout, logging, configuration, and tests. Use unchecked exceptions for domain errors; wr

This is an excerpt. Refer to the complete source and its current requirements.