#marten
marten

Using Event Sourcing? Prefer the Decider over AggregateRoot

Jeremy D. Miller strongly recommends that Event Sourcing developers model domain logic with the Decider pattern instead of the older AggregateRoot pattern. He explains why pure decide functions in Marten and Wolverine handlers are easier to reason about, test and debug. The post is a useful reference for anyone choosing a design for event-sourced .NET systems.

Storing and Querying a Hierarchy of Types with Marten

Jeremy D. Miller shows how Marten stores a class hierarchy in one PostgreSQL table and queries it with LINQ, without the table-per-type or table-per-concrete-type decisions EF Core requires. He also covers subtype-specific partial indexes and duplicated fields. For teams weighing document storage against EF Core inheritance mapping, it is a useful comparison.