I gave a talk at Wroclove.rb, in Poland, this April. It was originally going to be about the Actor Model in Event Sourcing, but I changed it to Building reactive systems with Ruby and Event Sourcing.
Basically I’ve been building a little web framework - as one does- designed for building command-oriented workflows where the UI just reacts to state changes in the backend. This is still work in progress, and it started as patterns extracted from demo apps I’ve been building for showcasing Sourced, my (also WIP), Event Sourcing toolkit.
The more general guiding principle being that I want my tools to let me implement the domain in terms of its operations, instead of what technical layer each operation lives in.
Right after Wroclove.rb, I did a workshop on Event Sourcing and Ruby at Haggis Ruby, in Glasgow, UK. In was my first workshop at a conference, and I tried to present a narrative from what Event Sourcing is, how you can use it in Ruby today, to what it could be, showing some of the work I’ve been doing to achieve a single, cohesive programming model with reactive, real-time UIs in the frontend and auditable, replayable and autonomous services in the backend. The workshop was not recorded, but if you’re curious about what any of those words mean, watch the video above!
A huge thank you to the organisers at both conferences. I had a great time and brilliant conversations with like-minded people.
PS: These two talks came on the back of a two-week holiday visiting family in Chile. It made for a pretty intense April overall.
