How we buid and mitigated our Spring Boot applications to Kotlin
summary
Migration follows incremental module/layer moves with concrete steps: use IntelliJ’s convert Java file to Kotlin, update Maven POM and Java 11 settings, drop Lombok for data classes and null-safety, replace null checks with Elvis and scoped functions (let/also/run), turn blocking clients (3 clients: Kafka, REST, SOAP) into nonblocking code using suspend functions and coroutines and launch/async, adopt extension functions and runCatching and extension methods for cleaner error handling, keep unit/integration tests, deploy working services after small, safe commits.
AI-written summary · about
chapters (17)
- 0:00Migrating to Kotlin
- 3:06Kotlin vs Java issues
- 6:06Team and project prep
- 9:03Migration step by step
- 13:01Convert Java to Kotlin
- 15:13Remove Lombok simplify
- 17:20Constructor injection less boilerplate
- 21:29Reactive clients null safety
- 24:00Readability with extensions
- 27:03Replace if with 'when'
- 29:11Coroutines non-blocking
- 31:22Coroutines in Spring Boot
- 32:06Blocking to coroutines
- 36:56Suspension vs threads
- 40:18Coroutines benefits
- 43:12Takeaways best practices
- 44:40Q&A
related talks
36mUpgrade Time: Choose Java 11+ or the “Other” One…Kotlin
52mSpring into Kotlin: How to Make the Magic even more Magical
02h 14mFrom Spring Boot 1 in Java to Spring Boot 2 in Kotlin
48mSpringing into Kotlin
45mWhy Spring Loves Kotlin
44mKotlin and Spring Boot, a Match Made in Heaven
01h 05mWhy Spring Loves Kotlin
47mWhy Spring ❤ Kotlin