event-sourcing   528

« earlier    

Event Sourcing made Simple – Kickstarter Engineering
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 
3 days ago by zmoog
Event Sourcing made Simple – Kickstarter Engineering - https://kickstarter.engineering/
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 
10 days ago by perezgb
Event Sourcing made Simple – Kickstarter Engineering
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 
16 days ago by ehayes
base_event.rb
Kickstarter's "Drip" project uses Event Sourcing, and this is all their library code.
event-sourcing  ruby  rubyonrails 
28 days ago by DivineDominion
Event Sourcing made Simple – Kickstarter Engineering
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 
28 days ago by philiphagen
Event Sourcing made Simple – Kickstarter Engineering
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

« earlier    

related tags

active-record  activerecord  actor-model  actor  ai  akka  analytics  ar  architecture  article  articles  asynchronous  aws-lambda  aws  banking  best-practices  business-logic  casestudy  clojure  cloud-native-java  code  commanded  continuous-delivery  cqrs  database  databases  ddd  design-pattern  design-patterns  dev  development  docker  done  dot-net  elixir  encryption  event-driven  event-processing  events  eventsourcing  for_snap  from:marten  gdpr  gnatsd  go  golang  graphql  greg-young  grpc  haskell  immutability  infoq  interesting  java  javascript  json  kafka  martin-fowler  microservices  nact  nats  natsd  netflix  node  pdf  people  php  postgres  presentation  privacy  programming  rails-framework  rails  reasonml  redux  ruby-lang  ruby  rubyonrails  rules-engine  samza  scalability  sequel  software-architecture  software  stream  versioning  video  webapp  webarch  work 

Copy this bookmark:



description:


tags: