Tuhrig.de Website Review

About a month ago I published a short article about Kotlin, Spring Boot and DynamoDB. The post shows a basic setup for DynamoDB with Kotlin and Spring Boot. However, it doesn’t show a lot of aspects related to typical database implementations such as auditing or During the last week I implemented my first persistence layer with DynamoDB using Spring Boot and Kotlin. As I stumbled over a couple of obstacles, I decided to summarize what I did and how my final implementation looked like. Dependencies The dependencies are pretty Some weeks ago I published a demo project on GitHub showing a Domain Driven Design with Kotlin. You can find the original blog post right here. Now I took the approach one step further and added Event Sourcing to the demo. Here’s what I did. Event Sourcing The basic I recently read Clean Architecture by Robert C. Martin. The book gives a simple advice: don’t depend on details! For Uncle Bob details are things like the database or message broker. Your architecture shouldn’t depend on the actual used implementation of those details. Three years ago I wrote a blog post with the provoking title “Don’t use Optionals for data repositories“. The post received a couple of critical comments and I had the feeling that I didn’t made my point clear. This week I stumbled over the same topic again, but I recently worked on a library for using AWS Kinesis in Spring Boot. As many other libraries, this particular one provided a powerful configuration. To implement the configuration, we used Spring Boot’s @ConfigurationProperties (as described here). This article gives some Updating data is one of the most frequent use-cases in applications. But it might also be a painful task which results in a bunch of ugly code. I recently stumbled over a typical update scenario in a Domain-Driven-Design (DDD) application. In the following, I want to Usually we use Spring’s @Configuration to define some special beans. A clas*ic example is the definition of a data source: