Spring Office Hours: Episode 53 - Structuring your Spring Boot Applications

Join Dan Vega and special guest Ted Young as we discuss how to structure your Spring Boot applications. In this episode, we will explore various options for organizing your code, such as package by layer, package by feature, onion architecture, and hexagonal architecture. Join us live and don't forget to bring your questions!

[@zahiyoussef2551]

Thank you so much i love youu , keep doing so much like those brodcasts❤❤🇲🇦

[@NilsElHimoud]

Two arguments in favor of package by feature: 1) Logging. Loggers are hierarchical. If you have grouped your classes by feature it allows you to activate the debug log for the feature by just changing the log level for the package of the feature. With package by layer you would need to change the log levels for many individual classes to get the whole picture. You lose the ability to set the log level for a group of strongly coupled classes. 2) Extracting microservices. Imho it is a good idea to start a new software with a modulith and only extract microservices when you see the need. With package by feature it is much easier to pull out some functionality and put it into a microservice.

[@bmamatkdyr]

my next target is set 🎯

[@protagorasfromabdera8653]

Please make videos in 1080p, code couldn't be clearly seen in big monitor.

[@SuperAdil08]

Thx Sir

[@JaisinghaniSagar]

17:00 start

[@alexandersmirnov4274]

please give github repo link

[@JitterTed]

See my comment for GitHub link for Ensembler. Or was there another repo you wanted a link for?

[@tdan89]

Check 01:01:54