Event sourcing for smooth brains: building a basic event-driven system in Rails
Event sourcing is a jargon filled mess, but we can build a lean version with just ActiveRecord, callbacks, and a bit of boring Rails code
**Event sourcing** is a jargon filled mess that is unapproachable to many developers, often using five dollar words like "aggregate root" and "projections" to describe basic concepts.
But lately I have been building with a very basic, dumbed down version of event sourcing (I call this "event sourcing for smooth brains") and I can see how aspects of this model can be a great fit for a boring Rails monolith.
Why would I want to use event sourcing for part of my app?
A basic schema for events tables that anyone can understand
Using Rails callbacks as the mechanism for dispatching and processing events
Practical examples of how complex features become easy, boring code
👉 Read it here: Event sourcing for smooth brains: building a basic event-driven system in Rails
📣 Thoughts? Join the discussion on Twitter
Stay boring!
- Matt