14:45 - 15:45
Software that has multiple domains needs code which maps between them. The reasoning behind this is, that domains have to be decoupled from each other. This is especially important in layered architecture, a style that is widely used in today’s software projects. Having layers in the application – usually a persistence layer, an application layer and a presentation layer – enforces separation of concerns and decouples the data models from each other. But: Does it really? In this session I will share some thoughts on the up- and downsides of layered architecture, boilerplate code, a common JPA antipattern, why "decoupled classes" do not mean "decoupled data" and how we could make our lives easier, if we let the database do what it does best: transform data.