code simple { }

TL;DR Treat CloudEvents as the envelope for versioned, traceable domain aggregate snapshots.

The Meta-Experience: Using AI to Build AI Tools In the world of software development, we often talk about eating our own dog food.

TL;DR: Use "Events as a Data Product" of your BoundedContext in the Data-Mesh by applying 'Data on the outside' thinking using KAPPA architecture.

Event sourcing gives us a few benefits such as in-built audit logs, replay/rebuilds, multiple projections (read models), and non-blocking writes.

Back in 2005, Pet Helland has written this excellent white paper called “Data on the Outside versus Data on the Inside“.

Not only does the event sourcing inherit complexities of the asynchronous world, but it also amplifies them.

When it comes to the events, the big debate is about the contents of its body.

In real-world monoliths, code of a single bounded context is spread across many dimensions.

Besides an opportunity for my team to return to the comforts of dotnet from nodejs, performance improvements in asp.net core (as evident from the latest round i.e. 16 of Web Framework Benchmarks by TechEmpower) was another good reason to trial it for an i…

Furthermore to my previous post where I tried to compare events and commands, here I am presenting a scenario where they complement each other.