"Eventual consistency" is a descriptive term, but not the right framing for systems built that way. "Convergent consistency" speaks more directly to the trade-offs involved.

Chilean newspapers have mastered the art of partisan spin. Latest headline: “Poverty rates in half of the regions are above the national average!”

Power often turns people into jerks. People who were already jerks turn into galaxy-size assholes.

I've said it before, but I'm fascinated by how thinking in terms of Event Sourcing almost inevitably leads you to the Actor Model, and to re-evaluate what you thought you knew about OOP.

I've been using Ruby along these lines for many years now. It's not so much that you should avoid classes. Rather, class inheritance should not be assumed to be a public API. You can still have procedure-like components that use classes for private state management. www.youtube.com/watch?v=sjuC...

“Dad, I don’t get how people have babies after getting married. How does a party with fancy food and clothes make people’s cells combine and make babies?”

Durable streams FTW electric-sql.com/blog/2025/12...

"Oh, if I record state changes in my app as entries in a ledger, then I can process entries for the same entity sequentially and materialise current entity state without deadlocks". Lots of developers invent event sourcing sooner or later 😀 Don't stop there! Now think through the implications.

State machine libraries for ActiveRecord are an anti-pattern.

The second batch of tickets is almost gone - we can't wait to see you all at #wrocloverb! 🤩 If you'd like to join us as a speaker, our CFP is still open and we're waiting to hear your ideas! Inspire your fellow developers, submit your talk here ➡️

Let's kick off the new week with exciting news - a new batch of tickets just dropped! 🥁 Don't miss your chance: grab your ticket and see you on April 17-19, 2026 at #wrocloverb ➡️ https://buytickets.at/wrocloverb/1903580

I love what @ismaelcelis.com is cooking around #eventsourcing in #Ruby. His blog post inspired me to create github.com/jandudulski/.... I'm more than happy that he'll speak at @wrocloverb.com 2026 🥳 Second batch of tickets will be released on Monday around 10 AM CET 🎅. Make sure your F5 is warm 😎

Santa is very generous to us today - he’s bringing two great announcements: 📣 Let’s welcome our first speaker - @ismaelcelis.com will join us to explore Event Sourcing and the Actor model in Ruby! 🎟️ The second batch of tickets goes on sale on Monday, Dec 8 at 10:00 CET - don't miss it!

Just submitted the most click-bait conference talk title to date

@balkanruby.bsky.social 's "hot take" format sounds appealing. I do have a few of those!

"We can't deploy the change to service A until we've deployed the change to service B" <== These are not "micro services", it's just a distributed monolith. (I've built my fair share of these ✋)

Happy December folks - with my ScotRUG organising hat on, our last meetup for the year is scheduled for next week, Thursday 11th December in the Quaker Meeting house on Victoria terrace. We'll be looking forward to the Ruby 4.0 release, and chatting about this and that. scotrug.org/2025/12/04/r...

I started playing with a DSL for event-sourced Reactors to publish an ephemeral notification after processing a message (for real time UI updates). It already does this, but I want a tighter end-to-end integration out of the box.

Next thing I want to try with Event Sourcing is projectors that trigger arbitrary code when they're "caught up" with their events. Ex. a new "Report v2" projector to replace the current one. You set it to build from all events. When it's "done", it flips a feature flag to start showing in the UI

Video of my Ruby and Event Sourcing talk at LRUG in November. In the second half I describe how I'm architecting the backend. lrug.org/meetings/202...

The "make code easy to delete, not easy to change" motto is resonating more and more with me...

ActiveModel's mutable attributes interface is such a bad idea. You only need to instantiate a form once per-request, with all attributes needed. Why explode the API unnecessarily with attribute setters!

I check my spam folder sometimes 😂

Commencing talk proposals for 2026 conferences.

So, this Ruby performance bottleneck has come down to either my code, or Jeremy Evans’. I think I know where to put my money.

I've been researching and playing with Event Sourcing and related patterns for years now, but it's an expensive hobby. If anyone's interested in (paid) introductions to the patterns and ideas, or workshops on the matter, hit me up! I honestly believe understanding it can provide a lot of value.

"Event Sourcing is about meaning, not volume". Great article on an important distinction docs.eventsourcingdb.io/blog/2025/11...

really good series on durable execution and workflows jack-vanlightly.com/blog/2025/6/...

“Papá, yo ya sabo hablar español!”

This 👇

If you’re just learning about Event Sourcing, you’ll come across the concept of an “aggregate root” (or you might already know it from DDD). This will lead you down the wrong mental model and only cause confusion. Luckily, the core ideas being masked by aggregates are rather simple!

The Arazzo spec, for describing API workflows, looks interesting spec.openapis.org/arazzo/lates...

I did a two-day introduction to Event Sourcing and Event Modelling workshop at a UK bank and… I think it went well?

Quite a few messaging/event-sourcing toolkits treat the ability to re-play events as an edge case and leave implementation mostly up to you (and it's the hardest part!). But the underlying property is the ability to have autonomous components, which IMO is the killer feature.

Optimising Sourced's real-time connections

Cohesion: "things that change together, go together" Procedural cohesion: "things that form part of the same workflow, go together". Logical cohesion: "things that implement the same technical pattern, go together". The last one makes the most initial sense, but provides the least value.

“Dad, why would anyone want to have an EATEN MESS for pudding?!”

Health-wise, I’m pretty sure the haggis and the black pudding in this breakfast cancel each other out.

The English countryside is lovely but it always strikes me as missing something at first, and then I realise it’s the looming mountains all around I grew up with.

On my way to Edinburgh for this evening’s Durable Messaging in Ruby talk at ScotRUG

Good talk on eventual consistency www.youtube.com/watch?v=8ybq...

🌸 Hanami 2.3 is here, and it’s racked and ready! This is our biggest release yet. Rack 3, resource routes, and so much more. hanamirb.org/blog/2025/11...

@matthewford.bsky.social great to hear you on Code with Jason!

Today in #ruby and #eventsourcing : test an entire workflow composed of multiple reactors sending messages to each other, all in-memory, and assert the full workflow as the trail of events left behind. No databases hurt in the process.

I think this is a pretty nice way to test event-sourced projectors

I'll be at today's London Ruby User Group meet-up, speaking about Event Sourcing, eventual consistency and durable messaging patterns. Show up if interested! lrug.org

Are you ready for the Scottish Ruby User Group this week? We're to be joined by the fabulous @ismaelcelis.com to talk durable messaging, event sourcing and more! Also: you can just hang out with other Rubyists. Sign up and we'll see you on Thursday! www.meetup.com/scotrug/even...

I need to shave off 16 minutes from this talk somehow, without it losing meaning.

Autonomous components communicating by reading and appending messages to a log. This temporal decoupling is what enables the logical boundaries that most micro-services fail to achieve. Blocking direct calls = temporal coupling.

Re-playability and autonomy, two faces of the same coin.