Application.properties basics in Spring Boot - Performance & Optimization

Performance: Application.properties basics

MEDIUM IMPACT

This affects application startup time and configuration loading speed.

Configuring application settings for Spring Boot startup

Spring Boot

application.properties with only necessary, flat key-value pairs and minimal multiline values

Simpler properties file parses faster and uses less memory during startup.

📈 Performance Gainreduces startup blocking by 50-80 ms

Configuring application settings for Spring Boot startup

Spring Boot

application.properties with hundreds of unused or redundant properties, complex nested configurations, and large multiline values

Parsing a large and complex properties file increases startup time and memory usage.

📉 Performance Costblocks startup for 100+ ms depending on file size and complexity

Performance Comparison

Pattern	File Size	Parsing Time	Memory Usage	Verdict
Large, complex application.properties	100+ KB	100+ ms	High	[X] Bad
Minimal, flat application.properties	1-5 KB	10-20 ms	Low	[OK] Good

Rendering Pipeline

Spring Boot reads application.properties during startup before the application context initializes. The file is parsed into configuration objects used by the framework.

→File I/O

→Parsing

→Configuration Binding

⚠️ BottleneckParsing large or complex properties files slows configuration binding.

Optimization Tips

1Keep application.properties files small and simple.

2Avoid unused or redundant properties to reduce parsing time.

3Prefer flat key-value pairs over complex nested structures.

Performance Quiz - 3 Questions

How does a very large application.properties file affect Spring Boot startup?

A It improves startup time by caching properties.

B It increases startup time due to longer parsing and binding.

C It has no effect on startup time.

D It reduces memory usage during runtime.

DevTools: Spring Boot Actuator / Logs

How to check: Enable debug logging for Spring Boot startup and watch for configuration loading times in console logs.

What to look for: Look for long delays or warnings related to property binding or configuration parsing.

Practice

1. What is the primary purpose of the application.properties file in a Spring Boot project?

easy

A. To store configuration settings as key=value pairs

B. To write Java code for the application

C. To define HTML templates for the UI

D. To manage database schema migrations

Solution

1. Step 1: Understand the role of application.properties

   This file is used to store configuration settings in a simple key=value format.

2. Step 2: Compare with other options

   Writing Java code, defining HTML templates, or managing database migrations are done elsewhere, not in this file.

3. Final Answer:

   To store configuration settings as key=value pairs -> Option A

4. Quick Check:

   Config file = key=value pairs [OK]

Hint: Remember: properties file holds settings, not code or templates [OK]

Common Mistakes:

• Thinking it contains Java code
• Confusing it with HTML or template files
• Assuming it manages database migrations

2. Which of the following is the correct syntax to set the server port to 8081 in application.properties?

easy

A. server.port=8081

B. server-port: 8081

C. server_port=8081

D. port.server=8081

Solution

1. Step 1: Recall Spring Boot property syntax

   Spring Boot uses dot notation with key=value pairs in application.properties.

2. Step 2: Identify correct key for server port

   The correct key is server.port, and the value is set with an equals sign.

3. Final Answer:

   server.port=8081 -> Option A

4. Quick Check:

   Dot notation + equals sign = correct syntax [OK]

Hint: Use dot notation and equals sign for properties [OK]

Common Mistakes:

• Using underscores instead of dots
• Using colon instead of equals sign
• Swapping key parts order

3. Given this application.properties snippet:

spring.datasource.url=jdbc:mysql://localhost:3306/mydb
spring.datasource.username=root
spring.datasource.password=pass123

What will Spring Boot do with these properties when the app starts?

medium

A. Create a new database named 'mydb'

B. Ignore these properties because they are invalid

C. Start a web server on port 3306

D. Connect to MySQL database at localhost with given credentials

Solution

1. Step 1: Identify datasource properties

   The keys starting with spring.datasource configure database connection details.

2. Step 2: Understand Spring Boot behavior

   Spring Boot uses these to connect to the specified MySQL database with username and password.

3. Final Answer:

   Connect to MySQL database at localhost with given credentials -> Option D

4. Quick Check:

   Datasource properties = DB connection [OK]

Hint: Datasource keys configure DB connection automatically [OK]

Common Mistakes:

• Thinking it starts a web server on DB port
• Assuming properties are ignored
• Believing it creates the database automatically

4. What is wrong with this application.properties line?

server.port-8080

medium

A. The port number 8080 is invalid

B. The key and value are separated by a dash instead of equals sign

C. The key should be port.server instead

D. There should be no spaces around the dash

Solution

1. Step 1: Check property syntax

   Properties require key and value separated by an equals sign (=), not a dash (-).

2. Step 2: Validate the key and value

   The key server.port is correct, and 8080 is a valid port number.

3. Final Answer:

   The key and value are separated by a dash instead of equals sign -> Option B

4. Quick Check:

   Use '=' to separate key and value [OK]

Hint: Always use '=' between key and value in properties [OK]

Common Mistakes:

• Using dash instead of equals sign
• Swapping key parts order
• Thinking spaces fix the syntax

5. You want to add a custom property app.title in application.properties and access it in your Spring Boot code. Which of these steps is correct?

hard

A. Add app.title=MyApp in properties and access it with System.getenv("app.title")

B. Add app.title: MyApp in properties and read it with System.getProperty("app.title")

C. Add app.title=MyApp in properties and use @Value("${app.title}") in code

D. Add app.title=MyApp in properties and use @Autowired String app.title in code

Solution

1. Step 1: Add custom property correctly

   Use key=value syntax: app.title=MyApp in application.properties.

2. Step 2: Access property in Spring Boot code

   Use @Value("${app.title}") annotation to inject the property value.

3. Final Answer:

   Add app.title=MyApp in properties and use @Value("${app.title}") in code -> Option C

4. Quick Check:

   Custom property + @Value injection = correct [OK]

Hint: Use @Value("${key}") to inject properties in code [OK]

Common Mistakes:

• Using colon instead of equals in properties
• Trying to get property from environment variables
• Incorrect use of @Autowired for simple values