When Clean Architecture met Kotlin, A love story
summary
Kotlin replaces boilerplate with concrete patterns: data class for equals/hash/toString, val for immutability, extension functions that turn entity-to-domain mappers into fluent chains, operator overloads for cleaner access, and coroutines used as a pluggable use-case executor so tests run blocking while production runs background. Error handling swaps exceptions for sealed-class errors + Either/result. Examples include movie-entity → movie mapping with local/network fallback and a task-cost map/reduce pipeline.
AI-written summary · about
chapters (8)
- 0:00Introduction to love story
- 2:23What is Clean Architecture
- 3:45Kotlin’s elegance vs Java
- 8:05Mapping layers with Kotlin
- 12:39Why Kotlin feels functional
- 19:45Error handling in Kotlin
- 27:31Use cases and coroutines
- 31:21Summary and thank you
related talks
41mUsing Kotlin to implement Clean Architecture
30mWhat can Kotlin do for me?
01h 03mHow Kotlin makes your Java code better
41mMaking a Kotlin, Architecture Components, Rx and Coroutines sandwich
44mKotlin is for hipsters
31mDesign Patterns with Kotlin
29mShaping Your App's Architecture with Kotlin and Architecture Components
50mKotlin is as awesome as you've heard. Here's why.