Environment-based profiles in Spring Boot - Mini Project: Build & Apply

Environment-based Profiles in Spring Boot

📖 Scenario: You are building a Spring Boot application that needs to behave differently in development and production environments. Using environment-based profiles helps you switch configurations easily without changing code.

🎯 Goal: Create a Spring Boot application that uses dev and prod profiles to load different greeting messages. You will set up the data, configure the active profile, implement profile-based logic, and complete the application to display the correct message based on the active profile.

📋 What You'll Learn

Create a Map called greetings with keys dev and prod and their respective greeting messages.

Create a String variable called activeProfile to hold the current profile name.

Use if statements to select the greeting message based on activeProfile.

Complete the Spring Boot @RestController with a @GetMapping that returns the correct greeting.

💡 Why This Matters

🌍 Real World

Environment-based profiles let developers easily switch app behavior between development, testing, and production without changing code. This is common in real projects.

💼 Career

Understanding Spring Boot profiles is essential for backend developers to manage configurations and deploy applications safely across different environments.

1

Create the greetings data map

Create a Map<String, String> called greetings with these exact entries: "dev" mapped to "Hello Developer!" and "prod" mapped to "Welcome User!".

Spring Boot

// Create the greetings map with dev and prod messages
// Your code here

Hint

Use Map.of to create a small immutable map with the given keys and values.

2

Set the active profile variable

Create a String variable called activeProfile and set it to "dev" to simulate the current environment profile.

Spring Boot

Map greetings = Map.of("dev", "Hello Developer!", "prod", "Welcome User!");
// Set the active profile to "dev"
// Your code here

Hint

Just assign the string "dev" to the variable activeProfile.

3

Select greeting based on active profile

Create a String variable called message and use if statements to set it to the greeting from greetings map based on activeProfile. If activeProfile is "dev", set message to greetings.get("dev"), else set it to greetings.get("prod").

Spring Boot

Map greetings = Map.of("dev", "Hello Developer!", "prod", "Welcome User!");
String activeProfile = "dev";
// Use if statements to set message based on activeProfile
// Your code here

Hint

Use activeProfile.equals("dev") to check the profile and assign message accordingly.

4

Complete the Spring Boot controller

Create a Spring Boot @RestController class called GreetingController with a @GetMapping("/greet") method called greet() that returns the message variable. Include all previous code inside the class and method as needed.

Spring Boot

// Complete the Spring Boot controller class
// Your code here

Hint

Wrap your previous code inside a method greet() annotated with @GetMapping("/greet") inside a class annotated with @RestController.

Practice

1.

What is the main purpose of using profiles in a Spring Boot application?

easy

A. To separate configuration for different environments like development and production

B. To speed up the application startup time

C. To enable multi-threading in the application

D. To automatically generate database schemas

Solution

1. Step 1: Understand what profiles do

   Profiles allow you to define different settings for different environments, such as development, testing, or production.

2. Step 2: Match purpose with options

   Only To separate configuration for different environments like development and production describes separating configuration for different environments, which is the main use of profiles.

3. Final Answer:

   To separate configuration for different environments like development and production -> Option A

4. Quick Check:

   Profiles = environment-specific settings [OK]

Hint: Profiles separate configs by environment, like dev vs prod [OK]

Common Mistakes:

• Thinking profiles speed up startup
• Confusing profiles with threading
• Assuming profiles auto-generate schemas

2.

Which of the following is the correct way to activate a profile named dev in application.properties?

easy

A. profiles.active=dev

B. spring.profiles.active=dev

C. spring.active.profile=dev

D. spring.profile=dev

Solution

1. Step 1: Recall the correct property key

   The correct property to activate profiles is spring.profiles.active.

2. Step 2: Compare options

   Only spring.profiles.active=dev uses the exact correct key and value format.

3. Final Answer:

   spring.profiles.active=dev -> Option B

4. Quick Check:

   Activate profile with spring.profiles.active [OK]

Hint: Use spring.profiles.active to set active profile [OK]

Common Mistakes:

• Using spring.active.profile instead
• Omitting 'spring' prefix
• Using singular 'profile' instead of 'profiles'

3.

Given the following Spring Boot code snippet, what will be printed if the active profile is prod?

@Component
@Profile("dev")
public class DevService {
    public DevService() {
        System.out.println("DevService active");
    }
}

@Component
@Profile("prod")
public class ProdService {
    public ProdService() {
        System.out.println("ProdService active");
    }
}

medium

A. ProdService active

B. DevService active

C. Both DevService active and ProdService active

D. No output printed

Solution

1. Step 1: Identify active profile

   The active profile is prod, so only beans with @Profile("prod") will be created.

2. Step 2: Determine which constructor runs

   Only ProdService constructor runs, printing "ProdService active".

3. Final Answer:

   ProdService active -> Option A

4. Quick Check:

   @Profile("prod") runs only with prod profile [OK]

Hint: Only beans matching active profile run constructors [OK]

Common Mistakes:

• Assuming both beans run regardless of profile
• Confusing dev and prod profiles
• Thinking no output prints if profile mismatches

4.

Consider this Spring Boot configuration snippet in application.properties:

spring.profiles.active=dev,prod

What is the problem with this configuration?

medium

A. Multiple profiles can be active simultaneously, so no problem

B. Profiles should be separated by semicolon, not comma

C. Activating both dev and prod profiles together can cause conflicts

D. spring.profiles.active cannot be set in application.properties

Solution

1. Step 1: Understand multiple active profiles

   Spring Boot allows multiple profiles active at once, but dev and prod usually have conflicting settings.

2. Step 2: Identify the issue

   Activating both dev and prod together can cause unexpected behavior or conflicts in configuration.

3. Final Answer:

   Activating both dev and prod profiles together can cause conflicts -> Option C

4. Quick Check:

   Dev and prod active together causes config conflicts [OK]

Hint: Avoid activating dev and prod profiles simultaneously [OK]

Common Mistakes:

• Thinking comma separator is invalid
• Believing multiple profiles never cause issues
• Assuming spring.profiles.active can't be set in properties

5.

You want to create a bean that only loads when test profile is active and another bean that loads for all profiles except test. Which annotation setup is correct?

hard

A. @Profile("test") on first bean, no annotation on second bean

B. No need for @Profile, beans load automatically

C. @Profile("test") on first bean, @Profile("prod") on second bean

D. @Profile("test") on first bean, @Profile("!test") on second bean

Solution

1. Step 1: Use @Profile("test") for test-only bean

   This ensures the first bean loads only when the test profile is active.

2. Step 2: Use @Profile("!test") for all except test

   The negation !test means the second bean loads when test is not active.

3. Final Answer:

   @Profile("test") on first bean, @Profile("!test") on second bean -> Option D

4. Quick Check:

   Use @Profile("!profile") to exclude a profile [OK]

Hint: Use @Profile("!test") to exclude test profile [OK]

Common Mistakes:

• Not using @Profile on second bean causes it to always load
• Using @Profile("prod") limits second bean to prod only
• Assuming beans load automatically without profiles