“We can solve any problem by introducing an extra level of indirection” — Event Sourcing is the privileged model to do it. The idea of Event Sourcing is the following: to capture and save the changes of an application state as events. …

Do you know why society is producing the most qualified generation ever that cannot find a job? And why do they feel so entitled they believe the world owes them everything? I’ll tell you a tale. Once upon a time, there was a tribe of hunters. …

6. “Tell-don’t-ask” — “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” — Martin Fowler One of the most covered subjects on software development is how to create clean code, or as Martin Fowler says, code that humans can understand. Although extensive literature exists…

Debt is a good analogy to explain what happens with code if no care is taken: Debt grows if not payed. It can lead to chronic abuse. Cumulative debt grows exponentially. Eventually leads to bankruptcy. However It can be useful if tactically used. Can be a leverage if well managed…

I’ve seen many implementations of Event Sourcing that use a message broker to publish events to the read models. I’ve used that pattern and contributed to ES “frameworks” that implement that pattern. I think It is a bad idea. I’ll explain why: 1) Writing to the event store AND…

Intro Microservices are an architectural pattern that allows big software systems to be break in smaller parts. Each microservice can be developed, maintained, deployed and operated independently. Microservices share the same general principles of any modular architecture: break the system into smaller, independent, loosely coupled modules that communicate using a well…

As a student I never liked language subjects. Portuguese, English, French. But now I regret not have taken more advantage of it. Specially the French. Portuguese is my main language and English is so global that you would learn it anyway. But French and others escaped. Although I regret not…

You can read the part 1 here. You can read the part 2 here. In the last parts it was presented an evolutionary path towards an event driven architecture to support multiple read models. We ended with an architecture with a relational database that supports write operations where the business…