Environment-based profiles in Spring Boot - Step-by-Step Execution

Concept Flow - Environment-based profiles

Start Application

↓

Check Active Profile

↓

Load Profile-Specific Config

↓

Initialize Beans with Profile

↓

Run Application with Config

↓

End

The application starts, checks which profile is active, loads the matching configuration, initializes beans accordingly, and runs with that setup.

Execution Sample

Spring Boot

spring.profiles.active=dev

@Configuration
@Profile("dev")
public class DevConfig {
  // dev beans
}

This code activates the 'dev' profile and loads beans only when 'dev' is active.

Execution Table

Step	Action	Profile Active	Config Loaded	Beans Initialized	Result
1	Start Application	none yet	none	none	Application starting
2	Read spring.profiles.active	dev	application-dev.properties	none	Dev profile active
3	Initialize Beans	dev	application-dev.properties	DevConfig beans	Beans ready for dev
4	Run Application	dev	application-dev.properties	DevConfig beans	App running with dev config
5	End	dev	application-dev.properties	DevConfig beans	Application running

💡 Application runs with the 'dev' profile active, loading dev-specific config and beans.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
activeProfile	null	dev	dev	dev
configLoaded	none	application-dev.properties	application-dev.properties	application-dev.properties
beansInitialized	none	none	DevConfig beans	DevConfig beans

Key Moments - 2 Insights

Why does the application load dev beans only when the 'dev' profile is active?

Because @Profile("dev") annotation tells Spring to initialize those beans only if the active profile matches 'dev', as shown in execution_table step 3.

What happens if no profile is set in spring.profiles.active?

Spring loads default config and beans without any profile-specific ones, so profile-specific beans are not initialized. This is implied by the 'none yet' profile in step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the active profile at step 2?

A dev

B prod

C none

D test

💡 Hint

Check the 'Profile Active' column at step 2 in the execution_table.

At which step are the dev beans initialized?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Beans Initialized' column in the execution_table.

If spring.profiles.active was set to 'prod', how would the configLoaded variable change?

A It would be null

B It would remain application-dev.properties

C It would be application-prod.properties

D It would be application-default.properties

💡 Hint

Refer to variable_tracker and how configLoaded matches the active profile.

Concept Snapshot

Environment-based profiles in Spring Boot:
- Use spring.profiles.active to set the active profile.
- Annotate beans/config with @Profile("name") to load conditionally.
- Spring loads profile-specific properties like application-dev.properties.
- Only beans for the active profile initialize.
- Helps separate configs for dev, test, prod environments.

Full Transcript

When a Spring Boot application starts, it checks which profile is active by reading the spring.profiles.active property. Based on this, it loads the matching profile-specific configuration file, such as application-dev.properties for the 'dev' profile. Then, Spring initializes only the beans annotated with @Profile matching the active profile. This way, the application runs with environment-specific settings and beans. If no profile is set, default configurations and beans load. This mechanism helps developers easily switch between environments like development, testing, and production by changing one setting.

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