CQRS in Go — Part 4: PostgreSQL as an event store

CQRS in Go series: Part 1 : the aggregate, Transition() and Clone() Part 2 : command handlers without side effects Part 3 : sagas and event choreography Part 4 : PostgreSQL as an event store The first three parts laid the groundwork: immutable aggregates, pure command handlers, sagas through choreography. One central question remains — where do we persist the events? This part answers that question using PostgreSQL as an append-only event store, with no additional dependencies. Why PostgreSQL an