Ismael Celis
@ismaelcelis.com
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.
November 13, 2025 at 11:22 AM
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
November 13, 2025 at 10:55 AM
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...
Keynote: You Keep Using That Word - Sam Newman | MQ Summit 2025
YouTube video by Code Sync
www.youtube.com
November 12, 2025 at 3:29 PM
Good talk on eventual consistency www.youtube.com/watch?v=8ybq...
Reposted by Ismael Celis
🌸 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...
This is our biggest release yet. Rack 3, resource routes, and so much more.
hanamirb.org/blog/2025/11...
Hanami 2.3: Racked and Ready
Our biggest release yet. Rack 3, resource routes, and so much more.
hanamirb.org
November 12, 2025 at 1:20 PM
🌸 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...
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!
November 12, 2025 at 9:37 AM
@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.
November 11, 2025 at 11:14 PM
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
November 11, 2025 at 2:58 PM
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
LRUG | London Ruby User Group
The London Ruby User Group (LRUG) meets on the 2nd Monday of the month for talking and socialising (about Ruby).
lrug.org
November 10, 2025 at 10:25 AM
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
Reposted by Ismael Celis
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...
Durable messaging and related patterns in Ruby, for fun and profit, Thu, Nov 13, 2025, 6:00 PM | Meetup
Hallowe'en is almost upon us - get ready for [the Samhuinn celebrations](https://beltane.org/about-samhuinn/) maybe carve yourself a neep as tradition suggests. And then? W
www.meetup.com
November 9, 2025 at 10:51 PM
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.
November 9, 2025 at 12:37 PM
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.
November 9, 2025 at 12:50 AM
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.
November 9, 2025 at 12:31 AM
Re-playability and autonomy, two faces of the same coin.
Playing with Given, When, Then helpers to test event-sourced Actors.
GIVEN these previous events
WHEN I dispatch a new command
THEN I expect these new events
Pure, behaviour tests, no database in sight.
GIVEN these previous events
WHEN I dispatch a new command
THEN I expect these new events
Pure, behaviour tests, no database in sight.
November 8, 2025 at 6:09 PM
Playing with Given, When, Then helpers to test event-sourced Actors.
GIVEN these previous events
WHEN I dispatch a new command
THEN I expect these new events
Pure, behaviour tests, no database in sight.
GIVEN these previous events
WHEN I dispatch a new command
THEN I expect these new events
Pure, behaviour tests, no database in sight.
Sourced's durable workflows are just event-sourced reactors under the hood, so they can participate in "conversations" with other actors just as well. This example holiday booking runs and retries steps sequentially.
November 8, 2025 at 12:19 PM
Sourced's durable workflows are just event-sourced reactors under the hood, so they can participate in "conversations" with other actors just as well. This example holiday booking runs and retries steps sequentially.
I'll never get tired of rebuilding event sourced projections
November 7, 2025 at 7:10 PM
I'll never get tired of rebuilding event sourced projections
Reposted by Ismael Celis
I shared a bit more detail about the morphing algorithm in Morphlex here. I also released Morphlex 1.0. joel.drapper.me/p/morphlex/
Better DOM Morphing with Morphlex
joel.drapper.me
November 7, 2025 at 11:45 AM
I shared a bit more detail about the morphing algorithm in Morphlex here. I also released Morphlex 1.0. joel.drapper.me/p/morphlex/
The TODO List pattern in Event Sourcing is such a simple way to orchestrate integrations with third parties, for example sending and tracking web hooks
November 7, 2025 at 11:46 AM
The TODO List pattern in Event Sourcing is such a simple way to orchestrate integrations with third parties, for example sending and tracking web hooks
The talk I’m preparing just split into two possible talks 😭
November 7, 2025 at 12:17 AM
The talk I’m preparing just split into two possible talks 😭
23 slides in, probably a third of the talk done. Onward.
November 6, 2025 at 6:21 PM
23 slides in, probably a third of the talk done. Onward.
I wrote a quick mixin with a basic ".on(message)" DSL to facilitate building message handlers that don't require full Event Sourcing semantics. Handler methods can still request full event history for a stream, so you can still build ES on top of this, if needed.
November 6, 2025 at 1:33 PM
I wrote a quick mixin with a basic ".on(message)" DSL to facilitate building message handlers that don't require full Event Sourcing semantics. Handler methods can still request full event history for a stream, so you can still build ES on top of this, if needed.
Got the Todo App demo working with the new event-sourced architecture, too. Again no UX changes, but it's good to have a couple of different demos to test-drive changes to the library.
November 5, 2025 at 5:41 PM
Got the Todo App demo working with the new event-sourced architecture, too. Again no UX changes, but it's good to have a couple of different demos to test-drive changes to the library.
I'm removing the ability to (easily) run immediately-consistent workflows in my Ruby Event Sourcing stuff. It's a self-imposed moratorium on the more familiar paradigm, to force me to focus and polish the eventually-consistent mode. Make the hard thing easy first.
November 5, 2025 at 11:54 AM
I'm removing the ability to (easily) run immediately-consistent workflows in my Ruby Event Sourcing stuff. It's a self-imposed moratorium on the more familiar paradigm, to force me to focus and polish the eventually-consistent mode. Make the hard thing easy first.
Today's rant: ismaelcelis.com/posts/2025-1...
Unfinished business
Web framework emphasis on sync web controllers vs async background jobs leads to incohesive workflows.
ismaelcelis.com
November 5, 2025 at 12:16 AM
Today's rant: ismaelcelis.com/posts/2025-1...
I need to use "cyclomatic complexity" in conversation more.
November 4, 2025 at 5:47 PM
I need to use "cyclomatic complexity" in conversation more.
Ok. Got the old Coffeeshop demo app working with the new architecture. Everything is eventually consistent, and all aspects of the UI are reactive (yet server-rendered).
November 4, 2025 at 4:55 PM
Ok. Got the old Coffeeshop demo app working with the new architecture. Everything is eventually consistent, and all aspects of the UI are reactive (yet server-rendered).