#eventsourcing

Event sourcing is a powerful pattern for tracking changes to application state, offering a robust...

A small write-up about something I built mostly for fun — and it works. Code:...

You've built an event-sourced system. Every state change is an immutable, appended event. You can...

Pillar article sull'Event Sourcing: come persistere gli eventi invece dello stato corrente per avere audit trail completo, replay e proiezioni illimitate.

State is a fold over events. Build an append-only store, apply() methods, and snapshots in plain PHP 8.4 — no library, under 100 lines.

Problem Statement Event Sourcing is a data storage pattern where you save every...

Your event store is already your audit log Almost every SaaS I've worked on ends up with...

A Filament plugin that routes every create, edit, and delete through your domain aggregates, without giving up the admin panel you already love.

The event-XOR-error invariant on command handlers. How to inform the caller of a business outcome without breaking the event/error separation, and why audit logging must be atomic.

Upcasters map old event versions forward at read time. How to evolve schemas, tell additive from breaking, and keep replay deterministic.

How an APAC video aggregator replaced a destructive CRUD moderation log with append-only events in S

Snapshot every 50 events, the docs say. Most teams snapshot every 10. Snapshot storage doubles every quarter. Here's the math you should use instead.