Member-only story
Spring Boot Profiles: How to Manage Environment-Based Configurations
Learn how to use Spring Boot Profiles to manage environment-specific configurations (dev, test, prod). Understand @Profile, application.properties, and application.yml settings.
This is a member-only article. For non-members, read this article for free on my blog: Spring Boot Profiles.
🚀 Introduction to Spring Boot Profiles
Spring Boot Profiles allow applications to load different configurations based on the environment (e.g., development, testing, production).
✅ Why Use Spring Boot Profiles?
✔ Manage Environment-Specific Settings (Database, API Keys, Logging).
✔ Easily Switch Configurations without modifying code.
✔ Use Different Beans for Different Environments (@Profile).
✔ Avoid Hardcoding Environment Variables.
📌 In this guide, you’ll learn:
✅ How Spring Boot Profiles Work.
✅ Using application.properties and application.yml for Profiles.
✅ How to Load Beans Conditionally Using @Profile.
✅ How to Switch Between Profiles.
1️⃣ How Do Spring Boot Profiles Work?
Spring Boot Profiles allow you to define multiple environment-specific configurations and activate them dynamically.
📌 Common Profiles Used in Projects:
2️⃣ Defining Profiles in application.properties
By default, Spring Boot loads application.properties, but we can create environment-specific files like:
application-dev.properties
application-test.properties
application-prod.properties📌 Example: application-dev.properties (Development Settings)
server.port=8081
spring.datasource.url=jdbc:h2:mem:devdb
logging.level.root=DEBUG📌 Example: application-prod.properties (Production Settings)
