Event Sourcing made Simple – Kickstarter Engineering


48 bookmarks. First posted by marionzualo 4 weeks ago.


Most software developers use a tool to keep track of code history. Git is a fantastic example that’s used widely across the industry. Type git log and you can see all the changes made to a codebase…
event-sourcing 
2 days ago by zmoog
Most software developers use a tool to keep track of code history. Git is a fantastic example that’s used widely across the industry. Type git log and you can see all the changes made to a codebase…
event_sourcing 
4 days ago by mac
Interesting approach to make events the basis of state on a web app.
ruby  rails  webdev  events 
8 days ago by amcewen
Event Sourcing made Simple – Kickstarter Engineering
eventsourcing  kickstarter 
9 days ago by kristofa
Wat? I thought I had a reasonably good understanding of git, but then I read - who knew you…
from twitter_favs
9 days ago by wm.wragg
Wat? I thought I had a reasonably good understanding of git, but then I read - who knew you…
from twitter
9 days ago by jaygooby
Most software developers use a tool to keep track of code history. Git is a fantastic example that’s used widely across the industry. Type git log and you can see all the changes made to a codebase…
event-sourcing  architecture  rails 
9 days ago by perezgb
In this post we’d like to talk about Event Sourcing. We’ll go over a high level introduction to Event Sourcing where we will highlight the four components that make a (minimal) Event Sourcing system: Events, Calculators, Aggregates and Reactors. We will then talk about how we implemented a (minimal) Event Sourcing Framework at Kickstarter for d.rip. And finally we’ll reflect a bit on the ah-ha moments and the challenges that we’re going through with this approach — 9 months after having started to work on d.rip and 4 months after launch.
kickstarter  engineering  database  events  git  states 
9 days ago by dlkinney
Most software developers use a tool to keep track of code history. Git is a fantastic example that’s used widely across the industry. Type git log and you can see all the changes made to a codebase…
rails  ruby  activerecord  eventsourcing 
10 days ago by geetarista
Event Sourcing made Simple – Kickstarter Engineering
from twitter
10 days ago by sammyrulez
tl;dr: Event Sourcing is to data what Git is to code. We’ve implemented a minimal event sourcing framework at Kickstarter to power d.rip . It’s simple and it…
from instapaper
10 days ago by hiroprot
Event Sourcing made Simple
from twitter_favs
10 days ago by demon386
Most software developers use a tool to keep track of code history. Git is a fantastic example that’s used widely across the industry. Type git log and you can see all the changes made to a codebase…
rails  ruby  event-sourcing  database 
15 days ago by ehayes
This is one of the most approachable descriptions of Event Sourcing and the key concepts behind it I have ever read. The animated diagrams help as well. Kickstarter’s specific implementation is very Rails and ActiveRecord heavy, but shows a lightweight application of the concepts.
26 days ago by thingles
Philippe Creux
event-sourcing  rails  ruby 
26 days ago by andyw8
tl;dr: Event Sourcing is to data what Git is to code. We’ve implemented a minimal event sourcing framework at Kickstarter to power d.rip . It’s simple and it…
from instapaper
27 days ago by indirect
Most software developers use a tool to keep track of code history. Git is a fantastic example that’s used widely across the industry. Type git log and you can see all the changes made to a codebase…
event-sourcing  programming  articles 
27 days ago by philiphagen
Based on those requirements, we decided to make the Event Sourcing framework an implementation detail of the back-end. The event sourcing implementation is not surfaced to GraphQL. The client application consuming the GraphQL API is not aware there is some Event Sourcing going on behind the scene.
We wanted the Aggregates to be regular ActiveRecord models that follow patterns that you’d find on a regular Rails application. This way, we could remove the Event Sourcing framework altogether and replace it with in-place data mutation: create!, update! and destroy! calls.
We looked at various Event Sourcing frameworks written in Ruby but most of them were actually too complex for our needs or would store data in a way that was too different from your regular Rails app. So we decided to build our own minimal framework. It’s about 200 lines of code.
activerecord  event-sourcing  ruby  rails 
28 days ago by stevenharman
Most software developers use a tool to keep track of code history. Git is a fantastic example that’s used widely across the industry. Type git log and you can see all the changes made to a codebase…
4 weeks ago by marionzualo