I got a suggestion recently about using .NET structs to represent DDD Value Objects to which I repeated what I’ve been saying and writing for several years now: structs are not a good choice for DDD Value Objects. But then I realized that I never actually dove into the details of why it is so.
So here it is, the blog post where we’ll talk about using .NET Value Types (structs) as DDD Value Objects and what effect it has on the domain model, performance, and mapping the model to the database using ORMs.
.NET Value Type (struct) as a DDD Value Object →
I’m starting a new series about unit testing anti-patterns. This post is the first article in that series.
When it comes to unit testing, one of the most commonly asked questions is: how to test a private method?
More about Unit testing private methods →
Today, I’d like to write about a simple and reliable way to implement domain events.
More about Domain Events →
In this post, I’m answering a reader’s question about how to combine an optimistic locking and automatic retry.
Optimistic locking and automatic retry →
This post is about a better implementation of Value Object.
Value Object: a better implementation →
In this post, I’d like to talk about what I think is one of the most damaging attitudes a company or a person can have in the field of software development: short-sighted perspective.
Short-term vs long-term perspective in software development →
I’m back to the regular posting schedule. No more game development, at least for now.
Always valid vs not always valid domain model →
Final part of my story about game development. First part, second part.