Are We Still Doing OOP? 🤔 Let's Tackle Anemic Domain Models Together

Java is an object-oriented (OO) language, but are we actually writing object-oriented code? In my years working as a software consultant I’ve seen plenty of codebases and with it, a repeating pattern: we keep splitting our data from our logic (myself included)! That clashes with the idea of object-oriented programming: adding behaviour to our objects. This antipattern has a name: Anemic Domain Models, and knowing how to tackle them will help you write more structurally sound and maintainable code. This is especially relevant nowadays, with design methodologies like Domain-Driven Design and Onion Architecture focusing our attention to structuring our code in a better way.

We’ll discuss the pitfalls of the Anemic Domain Model antipattern, where it can be found in your systems, but also how to battle it, and what the benefits are for writing code the real object-oriented way. So, if you are interested in coding practices, and want to learn more about the way we can write code, make sure to join this session!