Domain-driven Design with Kotlin
no recording on file
summary
Examines whether Kotlin language features—data classes, type aliases, operator overloading, sealed classes, etc.—make implementing tactical Domain-Driven Design less cumbersome than in Java. Uses the complex rule set of Dungeons & Dragons as the domain to demonstrate applying DDD patterns and Kotlin-specific constructs in practice.
AI-written summary · about
