Upgrading from Spring Boot 2 to 3 forced me to define my configuration properties in a better way.

Foojay.io's platform is a central hub for Java developers, offering insights into Java programming language, JVM ecosystem, and Java-related technologies. Through articles, tutorials, and community forums, Foojay.io offers insights into building scalable and maintainable Java applications. Developers can learn about Java language features, performance tuning tips, and best practices in Java development to write efficient and reliable software.

Foojay.io

Learn the proper way to define configuration properties in Spring Boot 3 after migrating from Spring Boot 2. Understand the issues with using Lombok and classes, and how to address them by using records. Discover how to validate configuration properties at start-up time and document your configuration for better IDE support.

The Proper Way to Define Configuration Properties in Spring

Spring boot 3: Some of my properties are suddenly empty!

The proper way to define your configuration properties

First, this website is not at all mobile friendly. Only the first 18 characters of each line of code is visible without scrolling sideways, and this is Java we’re talking about.
Second, it says “get rid of lombok”. This is terrible advice unless you love to write boilerplate. And besides, records aren’t going to cover every use case.
Finally, why do I have to constantly re-login to daily.dev. Is this a banking app? Does the DoD operate this site? Every few days I have to login to view the stuff from my email. It’s starting to be a dealbreaker.