Spring Profiles

spring.profiles.active=dev

// application-dev.properties
server.port=8081
spring.datasource.url=jdbc:mysql://localhost:3306/devdb

// application-prod.properties
server.port=8080
spring.datasource.url=jdbc:mysql://prod-server:3306/proddb

// Controller Example
import org.springframework.beans.factory.annotation.Value;
import org.springframework.web.bind.annotation.*;

@RestController
class ProfileController {

  @Value("\${spring.profiles.active}")
  private String activeProfile;

  @GetMapping("/profile")
  public String getProfile() {
    return "Active Profile: " + activeProfile;
  }
}

// Output:
// Active Profile: dev

• 1 Used to separate environment configurations.
• 2 Helps manage dev, test, prod setups.
• 3 Improves deployment flexibility.
• 4 Avoids configuration conflicts.

• 1 application-dev.properties
• 2 application-test.properties
• 3 application-prod.properties
• 4 Custom profiles like staging or QA

• 1 Spring Boot loads active profile.
• 2 Loads corresponding property file.
• 3 Overrides default configuration.
• 4 Runs environment-specific setup.

• 1 Separates environments cleanly.
• 2 Prevents deployment mistakes.
• 3 Improves maintainability.
• 4 Supports CI/CD pipelines.

• 1 Used in multi-environment deployments.
• 2 Used in cloud-based applications.
• 3 Used in CI/CD pipelines.
• 4 Used in enterprise systems.
• 5 SaaS products use Spring Profiles in services, dashboards, background jobs, and API workflows.
• 6 ERP and banking systems apply Spring Profiles with validation, logging, review, and rollback plans.
• 7 E-commerce and healthcare platforms use Spring Profiles carefully because reliability and data correctness matter.

• 1 A Java program first evaluates the surrounding context, then applies the Spring Profiles rules to the current data.
• 2 The important mental model is input, transformation, result, and failure path.
• 3 In production, the same flow usually sits inside a larger layer such as a controller, service, repository, job, or UI component.

• 1 Choose the simplest implementation first, then measure real workloads.
• 2 Watch for repeated work inside loops, unnecessary allocations, and slow I/O in hot paths.
• 3 Prefer clear data structures and stable APIs before micro-optimizing syntax.

• 1 Treat external input as untrusted until it is validated.
• 2 Avoid hardcoded secrets and never print sensitive values in examples or logs.
• 3 Use established libraries for authentication, encryption, parsing, and database access.

• 1 Hardcoding environment-specific values.
• 2 Not separating dev and prod configs.
• 3 Forgetting to activate profiles.
• 4 Mixing multiple environments in one file.
• 5 Skipping the small working example before adding framework code.
• 6 Ignoring null, empty, duplicate, and boundary inputs.
• 7 Mixing business logic, input handling, and output formatting in one place.
• 8 Using broad error handling that hides the real failure.
• 9 Forgetting to test the behavior after refactoring.
• 10 Adding clever code that future maintainers will struggle to read.

• 1 Use separate application-{profile}.properties files.
• 2 Never hardcode credentials.
• 3 Use environment variables when possible.
• 4 Activate profiles using spring.profiles.active.
• 5 Start with clear requirements and one minimal working example.
• 6 Use meaningful names that explain business intent.
• 7 Keep examples small enough to debug line by line.
• 8 Validate input at every trust boundary.
• 9 Handle errors explicitly and preserve useful context.
• 10 Prefer simple control flow over deeply nested logic.
• 11 Separate domain logic from I/O and framework code.
• 12 Write tests for normal, boundary, and failure cases.
• 13 Review security assumptions before production use.
• 14 Measure performance before optimizing.
• 15 Document non-obvious decisions close to the code or in project notes.
• 16 Use official documentation when behavior is version-specific.
• 17 Keep dependencies current and remove unused code.
• 18 Avoid hardcoded secrets, credentials, and environment-specific paths.
• 19 Log operational events without exposing sensitive data.
• 20 Design examples so learners can safely modify and rerun them.

• 1 Beginner: rewrite the example with different names and values.
• 2 Intermediate: add validation and handle one expected failure case.
• 3 Advanced: place Spring Profiles inside a small service-style design with tests.

• 1 Build a small Java console feature that demonstrates Spring Profiles.
• 2 Accept input, process it with the concept, print a clear result, and handle invalid input.
• 3 Add a README note explaining the design choice and two edge cases you tested.

• 1 If the program does not compile, check spelling, imports, braces, and file/class names first.
• 2 If output is unexpected, print intermediate values and verify each branch of the logic.
• 3 If the design feels complex, reduce it to the smallest working example and add pieces back one at a time.

• 1 Practice Spring Profiles with a second example from a business domain such as inventory, payroll, banking, or e-commerce.
• 2 Review related Java topics that cover data flow, error handling, testing, and clean design.
• 3 Compare your solution with official documentation and simplify anything you cannot explain clearly.