Addressing event-first concerns
Our event-first approach to building autonomous services is a bit of a paradigm shift. And as with any paradigm shift, there is plenty of opportunity for misunderstandings in the early adoption phases. This is completely understandable because we often have to unlearn the practices that we followed before. This can result in a resistance to change and the formulation of arguments against the change that turn out to be myths or anti-patterns.As architects, we need to make the effort to understand the source of these concerns, so that we can set the record straight and lead the product in the right direction. To this end, I am including the most common misconceptions that I have encountered. Let's start with a common misunderstanding of event lakes.
System of record versus source of truth
The event lake is a key element of our architecture. It provides a complete audit trail of all the actions and changes that occur within a subsystem. So, it seems...
