My presentation on DDD Europe 2022.
A software domain has the privilege to live in total isolation from any other component in the codebase, though it must be consumed by other components. By generalizing the interaction pattern to the domain one can greatly simplify these integration points.
In order to allow an event sourced software system to evolve I believe it to be important to issue coarse commands emitting granular events. In this post I explain why.
The aggregate is a well understood concept within DDD practices. The addition of event sourcing to the mix might however complicate things, and the once pretty domain is now in shambles. In this post I'll cover the addition of ES, while keeping the awesomeness of DDD in place.
I'd argue that those fostering a belief to exist as totally rational beings for the sole reason they deny the existence of emotions, might in fact be the most emotional beings around. This is what I'd call "the paradox of the rational mind".
I discovered there was a dependency incompatibility between EF Core 5 and SqlKata. I weighted my options, and decided it would be easier to revert back to EF Core 3, than to solve this dependency compatibility issue in another way.
In this post I describe how my introduction into a certain family ultimately led to the beginning of the end, slowly eroding the fundamentals currently defining the social dynamics within this family.
Many ideas surrounding suicide tend to shift the blame towards the person deciding to get rid of their life. In this post I introduce a paradox surrounding those supporting the suicidal person, also potentially being the cause of these suicidal ideations in the first place.
I describe the implementation of a cursor based GraphQL API following the Relay specification. Everything is covered, the specification, query composition, and even a real-world sample.
More often than not a software domain is required to deal with external components and service these must integrate with. Here are some considerations around these integration tasks.
In an effort to generalize event sourcing to the whole domain I try to adapt concepts previously developed for aggregates to other domain objects such as services, process managers, sagas and repositories.
Since it would be beneficial for commands to be able to issue multiple events reflecting its behaviour I modified an earlier approach to event sourced aggregates to allow this use-case.
Recently I have been looking for more flexible ways to search through text within a SQL database, and I stumbled upon a suggestion which indicated to use the so called Levenshtein distance.
If you'd like I'll drop new content straight into your mailbox. No need to keep hitting refresh on my site.Ps. feel free to hit reply on any mail you receive from me!
Looking at code through the "focal points" of the component might clarify a mismatch between the expected behaviour and that what is actually implemented. Organizing code accordingly to these focal points might provide a huge cognitive benefit to maintainers.
An improvement upon the previously proposed event sourced aggregate where command provides type information about its returned domain events.
With the "zombification of the mentally ill" I refer to a process where those dealing with mental health issues are muted due an underlying and unconscious fear one will eventually have to face their own trauma.
Recently I started playing around with Traefik on Kubernetes and wanted to request wildcard LetsEncrypt certificates.
If there is one thing I hate about web development it is creating input forms. In this post I'm about to explore some techniques to make form creation using React somewhat easier.
I ran a bunch of experiments to figure out how to access the filesystem from a .NET app running on Docker.
Some thoughts around drug use, personal identification with it, and its pathway to addiction
Having my brain eat itself while trying to interpolate two data sets to one another I came up with this working, though overly complicated solution. It works, but can be implemented in a much less convoluted mess.
In an attempt to make coordinates legible without resorting to maps I have tried an approach where I describe the position relative to a know point, such as a city, mountain top, or other landmark.