Dyskusje o pozycjach mogą być krępujące. Nie inaczej jest w przypadku Event Sourcing. Pozycja, wersja, rewizja, numer sekwencji. Nazewnictwo bywa mylące, a zrozumienie tych konceptów jest ważne do efektywnego używania event store'ów. Przeczytaj mój nowy artykuł i dowiedz się co jest co!

„Obsesja stanu” to nowy anty-wzorzec #EventSourcing, z którym postanowiłem się zmierzyć! To jeden z typowych problemów, gdy tkwimy w myśleniu o obecnym stanie, tabelach, zamiast rejestrować wynik operacji biznesowej. Przeczytaj więcej o tym, jak to diagnozować leczyć!

Jakiś czas temu napisałem, że "Czy to się skaluje?" nie jest pytaniem, ale mantrą. Zdałem sobie sprawę, że obecnie skalowanie w dół, może być bardziej krytyczne niż skalowanie w górę(biorąc pod uwage ARM, serverless, edge computing). Przeczytaj więcej w najowszym artykule.

“Knowing anti-patterns is as important as knowing any other patterns. Today I tackled #PropertySourcing. It's one of the most common anti-patterns while starting to implement #EventSourcing. Read more in my latest article!

With the simple tricks, you can make your Docker image less cluttered and build faster. In my recent article, I explained practical patterns on how to do that. I showed real-world samples with .NET and NodeJS applications.

When I started my career, SQL Injection and Cross-Site Scripting were perceived as sophisticated attacks. Mature admins installed MSSQL servers with the Internet turned off, because by default, open to the world was a potential source of the attack. Setting up the firewall wasn’t even a standard. Today we have easier. By using the cloud, many things are warranted. Suppliers protect us from basic break-ins. For instance, they’re blocking DDoS attacks and many other attacks that we don’t even know existed...

This week I decided to back to the basics of Event Sourcing. I explained how to build the current state from events in: - object-oriented style in C# - functional style in TypeScript. This is an essential part of treating events as the source of truth.

🚨 Quite often, to make our code simpler, we're trying to make our code more reusable and generic. I wrote an article with a warning that "generic" does not mean "simple". I did that on the example of #CQRS code evolution. Beware and have a read!

Today I want to invert the classical pro-agile drawing. Let’s talk about the devaluation of functionality that occurs in Agile projects and the cases when Agile is not enough.

Snapshots in Event Sourcing are a controversial topic. It's tempting to use them, but in my opinion, they should be used only when you had to, as a technical optimisation technique. Read more in my latest article!