Environment variables in configuration in Spring Boot - Performance & Optimization

Performance: Environment variables in configuration

MEDIUM IMPACT

This affects the application startup time and configuration loading speed, impacting how fast the app becomes ready to serve requests.

Loading configuration values for the application

Spring Boot

public class AppConfig {
    @Value("${CONFIG_VALUE}")
    private String configValue;

    // Environment variable injected once at startup
    // No runtime file parsing needed
}

Environment variables are injected once at startup, avoiding repeated file I/O and parsing.

📈 Performance GainReduces request latency by eliminating repeated config file reads

Loading configuration values for the application

Spring Boot

public class AppConfig {
    @Value("${config.value}")
    private String configValue;

    // Using a heavy config file parsing at runtime
    public void loadConfig() {
        // Reads large config file on every request
        Properties props = new Properties();
        try (InputStream input = new FileInputStream("config.properties")) {
            props.load(input);
            configValue = props.getProperty("config.value");
        } catch (IOException e) {
            e.printStackTrace();
        }
    }
}

Reading and parsing config files on every request blocks processing and slows response time.

📉 Performance CostBlocks request handling, increases response time by 50-100ms per request

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Reading config files on every request	N/A	N/A	N/A	[X] Bad
Using environment variables injected at startup	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Environment variables are read by the Spring Boot framework during application startup before serving requests, so they do not affect browser rendering but impact server readiness.

→Application Startup

→Configuration Loading

⚠️ BottleneckConfiguration Loading if done repeatedly or with heavy file parsing

Optimization Tips

1Use environment variables to inject config once at startup, not on every request.

2Avoid reading and parsing config files repeatedly during request handling.

3Environment variables improve backend readiness but do not affect browser rendering metrics.

Performance Quiz - 3 Questions

How do environment variables in Spring Boot configuration affect application performance?

A They increase DOM nodes and cause layout thrashing.

B They slow down browser rendering by adding extra CSS rules.

C They speed up application startup by avoiding repeated config file parsing.

D They block JavaScript execution on the client side.

DevTools: Network

How to check: Use Network panel to measure backend response times and check if config loading delays requests.

What to look for: Look for increased response times or delays that indicate blocking operations during request handling.

Practice

1. What is the correct way to reference an environment variable named DB_HOST in a Spring Boot application.properties file?

easy

A. Use #DB_HOST# to reference the environment variable.

B. Use ${DB_HOST} to reference the environment variable.

C. Use env(DB_HOST) to reference the environment variable.

D. Use DB_HOST directly without any syntax.

Solution

1. Step 1: Understand Spring Boot environment variable syntax

   Spring Boot uses ${VAR_NAME} syntax to inject environment variables into configuration files.

2. Step 2: Match the syntax to the variable name

   For the variable DB_HOST, the correct syntax is ${DB_HOST}.

3. Final Answer:

   Use ${DB_HOST} to reference the environment variable. -> Option B

4. Quick Check:

   Environment variable syntax = ${VAR_NAME} [OK]

Hint: Remember: Spring Boot uses ${VAR_NAME} for env variables [OK]

Common Mistakes:

• Using #VAR_NAME# instead of ${VAR_NAME}
• Trying to call env(VAR_NAME) like a function
• Using variable name without any syntax

2. Which of the following is the correct syntax to provide a default value for an environment variable PORT in application.properties?

easy

A. server.port=${PORT:8080}

B. server.port=${PORT:-8080}

C. server.port=${PORT=8080}

D. server.port=$PORT?8080

Solution

1. Step 1: Recall default value syntax in Spring Boot

   Spring Boot uses ${VAR_NAME:defaultValue} to provide a default if the environment variable is missing.

2. Step 2: Identify the correct syntax among options

   server.port=${PORT:8080} uses ${PORT:8080}, which is the correct way to set default port 8080.

3. Final Answer:

   server.port=${PORT:8080} -> Option A

4. Quick Check:

   Default value syntax = ${VAR_NAME:default} [OK]

Hint: Use colon : after variable name for default values [OK]

Common Mistakes:

• Using = instead of : for default values
• Using shell-style ${VAR:-default} which is invalid here
• Using $VAR without braces or default

3. Given the following application.properties snippet:

app.name=${APP_NAME:MyApp}
app.port=${APP_PORT:9090}

If the environment variables APP_NAME is set to TestApp and APP_PORT is not set, what will be the values of app.name and app.port at runtime?

medium

A. app.name=TestApp and app.port=9090

B. app.name=MyApp and app.port=9090

C. app.name=TestApp and app.port=null

D. app.name=null and app.port=9090

Solution

1. Step 1: Check environment variable APP_NAME

   APP_NAME is set to 'TestApp', so app.name uses this value, ignoring the default.

2. Step 2: Check environment variable APP_PORT

   APP_PORT is not set, so app.port uses the default value 9090.

3. Final Answer:

   app.name=TestApp and app.port=9090 -> Option A

4. Quick Check:

   Set var overrides default; unset uses default [OK]

Hint: Set env var overrides default; unset uses default [OK]

Common Mistakes:

• Assuming default is used even if env var is set
• Assuming null if env var is missing without default
• Confusing variable names or values

4. Consider this application.properties line:

database.url=jdbc:mysql://${DB_HOST}:${DB_PORT:3306}/mydb

When running the app, it throws an error because DB_HOST is not set. What is the best fix?

medium

A. Ignore the error; Spring Boot will use a fallback automatically.

B. Remove ${DB_HOST} and hardcode the host.

C. Set a default value for DB_HOST like ${DB_HOST:localhost}.

D. Change syntax to ${DB_HOST:-localhost} to fix it.

Solution

1. Step 1: Identify cause of error

   DB_HOST is not set and no default is provided, causing Spring Boot to fail resolving the variable.

2. Step 2: Provide a default value using correct syntax

   Use ${DB_HOST:localhost} to supply a default host if the environment variable is missing.

3. Final Answer:

   Set a default value for DB_HOST like ${DB_HOST:localhost}. -> Option C

4. Quick Check:

   Missing env var needs default to avoid errors [OK]

Hint: Always provide defaults for required env vars to avoid errors [OK]

Common Mistakes:

• Using shell syntax ${VAR:-default} which Spring Boot does not support
• Assuming Spring Boot auto-fills missing env vars
• Hardcoding values reduces flexibility

5. You want to configure a Spring Boot app to read a nested environment variable for a Redis URL with fallback defaults. Which application.properties line correctly uses environment variables REDIS_HOST and REDIS_PORT with defaults localhost and 6379 respectively?

hard

A. redis.url=redis://$REDIS_HOST:$REDIS_PORT

B. redis.url=redis://${REDIS_HOST:-localhost}:${REDIS_PORT:-6379}

C. redis.url=redis://${REDIS_HOST}${REDIS_PORT}

D. redis.url=redis://${REDIS_HOST:localhost}:${REDIS_PORT:6379}

Solution

1. Step 1: Recall Spring Boot default value syntax

   Spring Boot uses ${VAR_NAME:default} to provide defaults for environment variables.

2. Step 2: Check each option for correct syntax and completeness

   redis.url=redis://${REDIS_HOST:localhost}:${REDIS_PORT:6379} correctly uses ${REDIS_HOST:localhost} and ${REDIS_PORT:6379} with colon syntax and includes the colon separator between host and port.

3. Final Answer:

   redis.url=redis://${REDIS_HOST:localhost}:${REDIS_PORT:6379} -> Option D

4. Quick Check:

   Use colon : for defaults; include separators explicitly [OK]

Hint: Use ${VAR:default} and include separators like : explicitly [OK]

Common Mistakes:

• Using shell-style :- instead of : for defaults
• Omitting colon between host and port
• Using $VAR without braces or defaults