end-of-year hack: Sourced Deciders track command => event => command definitions. The idea is to use this to a). guard state machine transitions and b). generate documentation and diagrams, for example with a Mermaid integration #eventsourcing #ruby
=> View attached media | View attached media
=> More informations about this toot | More toots from ismasan@ruby.social
Very simple flowchart generated off this
=> More informations about this toot | More toots from ismasan@ruby.social
Bit more progress on this: events and commands are grouped (using Mermaid) by the modules that handle them, which in Sourced also map to concurrency boundaries. So this gives you a basic idea or what parts of a workflow are run linearly or concurrently from each other.
=> More informations about this toot | More toots from ismasan@ruby.social
Slightly better still, grouping the possible code paths within and across "Deciders"
=> More informations about this toot | More toots from ismasan@ruby.social
Managed to steal some minutes for this today. Buggy and still ugly AF, but I can show an #eventsourcing app's full flowchart, and drill down into specific flows within it.
=> More informations about this toot | More toots from ismasan@ruby.social This content has been proxied by September (3851b).Proxy Information
text/gemini