Embracing Clean Architecture in Spring Boot and Kotlin
summary
A Spring Boot + Kotlin demo app with two endpoints to add/list products plus two for attaching discounts evolves from a simple three‑layer JPA model into a domain‑centric core using ports/adapters: repository interfaces in the domain, JPA adapter implementations, and a pricing use case. Transactional boundaries move out of domain into Spring configuration, nullability and ORM leaks disappear, testability and replaceability improve, and the sample repo and slides are published for follow‑up.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 1:56What is software architecture
- 9:00Common architecture styles
- 13:31What is clean architecture
- 14:56Starting the demo with basic example
- 16:21Adding complexity to the example
- 18:08Refactoring to clean architecture
- 27:07Final architecture overview
- 31:26Symptoms of unclean architecture
- 35:57Additional tips and Q&A
related talks
41mUsing Kotlin to implement Clean Architecture
44mKotlin and Spring Boot, a Match Made in Heaven
59mSpring into Kotlin: How to Make the Magic even more Magical
50mBootiful Kotlin
58mSpring and Kotlin: A Winning Combination
48mKotlin for the back-end – Does the fancy code bring much value?
43mKotlin for Fun for Spring Fans
02h 14mFrom Spring Boot 1 in Java to Spring Boot 2 in Kotlin