An Event Store, whether it is an out-of-the-box solution or custom-built, needs to offer certain essential features and might offer some additional, advanced features. — What is an Event Store? An Event Store is a specialized storage solution for event sourcing. This can be an out-of-the-box solution such as EventStoreDB, a library or framework that offers the functionalities that an Event Store should have, with the underlying storage being either a RDBMS, a NoSQL, or Key-Value database (e.g. …

Well, as you all know Musk owns Twitter now and probably completely destroys it in no time, or at the very least invites a lot of bad actors, mostly from the far right spectrum. He already “reinstantiated” the overload of the nuts, Donnie Trump. …

The internet contains many confusing articles that mix Event Sourcing with EDA and CQRS. Let’s see what it is and what not. — I’ll probably not describe anything in this article that has not been written about 100 times. Sadly, as Event Sourcing gains more and more popularity, for each good article another five misleading articles are published. Partially because some people try to use Kafka as an Event Store. I have recently…

Don’t believe everything a company or some consultants want to sell you! — Before we start, if you only have a rough idea about what Event Sourcing is, you might have a look at this great article from Alexey Zimarev. Update: I just published my own intro to ES. Event Sourcing explained The internet contains many confusing articles that mix Event Sourcing with EDA and CQRS. Let’s see what it is and what not.medium.com

About the granularity of ports and adapters and how it influences the code structure — I did a major update of this article (3rd of June, 2022) after it was first published Motivation / Is this article for you? Hexagonal Architecture as an architectural pattern is not overly complex. Still, I remember that I spent some time finding out “where to put things” in the past. If you are not yet familiar…

There is no one-size-fits-all, but what I found in my career in (agile) software development is that teams are often too big rather than too small — Please pardon the clickbait title, I have to feed my kids. ;-) Now that I have your attention, here is a summary of what this article is all about The whole article is a bit tongue in cheek. The number of developers is less important than other factors, like team chemistry, collaboration, autonomy → how well the team works together!

Sometimes different paradigms are forces that pull our code in different directions. I’ll try to describe such a situation with concerns from Domain-Driven Design and Functional Programming. — Using the tactical patterns from Domain-Driven Design we sometimes have to inject dependencies into aggregates or entities, because they are necessary to fulfill the functionality of those domain objects, e.g.:

Pair Programming vs. Code Reviews seems to be the current tabs vs. spaces in our field — There is a lot of discussion about code reviews in my Twitter bubble lately, partially with some very strong opinions that code reviews are always a waste. This triggered some folks for sure and the latest and greatest is a tweet from a guy named Matt: FYI: He always…

While Go is not a functional programming language, functions are first-class citizens and offer some mighty features that we can leverage — I love the multi-paradigm approach of Go. We can implement things in an OOP fashion without the traps of inheritance (I’m opinionated here). On the other hand, we can work in a functional way. …