Spring Data JDBC - Taming the Beast
Mikhail Polivakha - Sberbank
Over the years Spring Data JDBC has gained a substantial amount of new features—single query loading, composite keys support, and many others. Being a more lightweight alternative to JPA solutions, more developers tend to choose Spring Data JDBC as their ORM.
Still, Spring Data JDBC requires a very specific and accurate design of aggregates. Designing the domain model of entities wrong can bring a lot of complexity along with performance-related problems. We don’t want that.
In this talk we’ll design the sophisticated domain model of aggregates. Starting small, we’re going to step-by-step add additional requirements to our system. Support of new requirements would push us to revisit the design of our domain model. We’re going to evolve it together, avoiding the common and less common problems.
