↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Building an Event Sourcing System in Rails, Part 1: What is Event Sourcing?

Event Sourcing is presented as a design pattern in which each change to data becomes an immutable event stored in chronological order. Those events are kept as a permanent history, and the current system state is derived from them.

Reading notes
#

  • Changes to data are stored as Event objects.
  • The Events have a fixed chronological order that can be replayed.
  • The Events cannot be changed or deleted for as long as they might be needed.
  • The example app centers on creating and destroying a User model.
  • The basic flow is that the client sends a request, the server creates and saves a User, and then saves an Event with the request and created User details.
  • Martin Fowler describes version-control systems like Git as a common example of Event Sourcing.
  • In that comparison, the commit log is the event store and the working copy is the system state.
  • For Rails, the article points to Kickstarter’s minimal Event Sourcing example and Arkency’s RailsEventStore library.
  • From the author’s experience, immutability means avoiding ActiveRecord.destroy and designing for permanence, such as using a deleted field.
  • Saving event payloads can expose sensitive data if they are stored outside auth features like has_secure_password.
  • Because events become the principal source of truth, naming and organizing event objects becomes more important and must be future-proof.
  • The next article will cover setting up a Rails app, building the BaseEvent class architecture, and implementing Events::User::Created and Events::User::Destroyed.