🗄️ How to store events in Event Sourcing

An event store sounds exotic, but it’s a database like any other. It keeps events grouped by the record they belong to, always adds new ones at the end, and gives you the guarantees you expect from a database. Once you see that, questions about performance, consistency and choosing a tool get much easier to answer.

The first articles explain that model and build a simple event store on PostgreSQL in an hour. They also show that relational databases already work this way inside. The next ones cover how other parts of the system keep track of the events they’ve already processed. The later articles look at the building blocks underneath, and at whether S3 or temporal tables can do the same job.

You don’t need all of this to use an existing event store. It helps you understand what it guarantees, and why.