Oct 26, 2018 - Events are forever... until they're not.

One of the founding principals of event sourcing is that events are forever, they cannot change or be deleted. You need to keep the entirety of history so that you can derive business value from rebuilding projections or adding new ones to answer new questions or build new features.

In a post GDPR world, this comes into conflict with users being able to assert control over their personal data you are processing. User requests are not the only reason you may need to delete or modify events - a change in requirements may lead to drastic changes in your model and a need to rethink the events in your system.

In this post I’ll explore some of the ways you can manage these situations.

There's more...

Oct 12, 2018 - On services.

I’m not really a fan of services, that is classes in your code base which are named something service. While I’m happy to admit that sometimes they do have a place much of the time when I see a class named something service, it has usually served as a dumping ground for business logic which someone couldn’t find a better place for. I too have fallen into this trap, so spurred on by a twitter thread posted in response to this article by Frederick Vanbrabant I decided to write up a few thoughts.

There's more...

Sep 5, 2018 - Paying for speaker expenses

This is a subject which comes up a lot. Should conferences be expected to pay for the expenses of their speakers? There are a lot of reasons that conferences give for not doing so, in this post I will explore some of these reasons and present my perspective from both the speaking side and organisation side as to why they are not good enough.

There's more...