Using Kotlin and Data Classes to set up Spring Boot with DynamoDB
summary
Kotlin data classes plus Spring Boot and DynamoDB cut boilerplate: repository CRUD and dynamic finders come from Spring Data DynamoDB, nested maps map directly into nested data classes, JSON blobs use type converters (custom converters allowed), and a composite key becomes a single ID class because the repository expects one ID. Local testing runs DynamoDB in Docker. JVM-required getters/setters are still needed for the ID fields so sometimes non-idiomatic Kotlin (no-arg constructor or defaults) is necessary.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:50DynamoDB
- 1:50DynamoDB Data
- 3:22Creating a Table
- 5:03JPA Provider
- 6:12Enable Repository
- 7:30Composite Key
- 9:54Map
- 10:10Load Map
- 12:07Load Data Class
- 12:35Type Converter
related talks
52mSpring into Kotlin: How to Make the Magic even more Magical
48mKotlin for the back-end – Does the fancy code bring much value?
59mSpring into Kotlin: How to Make the Magic even more Magical
48mSpringing into Kotlin
58mSpring and Kotlin: A Winning Combination
50mKotlin and Spring boot a pleasant experience and some rough edges
02h 38mKotlin Deep Dive
41mUsing Kotlin to implement Clean Architecture