http4k-connect VS dynamodb-kotlin-module

http4k-connect is a set of lightweight (zero-reflection) API libraries for connecting to popular third-party cloud services using http4k clients, along with Fake implementations for usage during local testing. It is based around the Connect pattern, which allows you to express client-side adapters in modular and composable way.

Great stack! Just out of interest , any reason you don't use Http4k connect for your AWS needs?

TBH, the official SDK dynamo client library isn't great for either. If you're looking for something lightweight, you could try http4k-connect - the dynamo client API is much nicer, does type-safety by plugging into the http4k lens system, and is zero reflection (using Moshi and generated adapters), which means you can simply cross compile to GraalVM. We're using it for native Kotlin Lambdas using the custom http4k Lambda runtime and it's 🚀🚀🚀. You can also use it backed by the OkHttp client wrapper if you want.

Dynamo is a great database to work with, but the mapper that comes with it isn't kotlin-friendly. You'll either have to make tons of compromises to make your data classes bean-compatible, or you'll have to find a plugin (for the v2 sdk) to support data classes. This one works well for me, but it doesn't seem to be popular at all, so YMMV.