ProcessManager/Saga docs and samples
See original GitHub issueWould be great to extend example module with sample ProcessManager
code.
Maybe showcase several aggregates/entities and process manager in a real world scenario.
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (7 by maintainers)
Top Results From Across the Web
How to implement Process Manager / Saga without ES and ...
Hi there, I am taking my first steps in the world of distributed computing and I am creating a small in-house ASP.NET 5.0...
Read more >Saga - Ecotone
Process Manager Saga PHP. Saga is responsible for coordination of long running processes. It can store information about what happened and make a...
Read more >snatch-dev/Chronicle: Implementation of saga pattern for .NET ...
Chronicle is simple process manager/saga pattern implementation for .NET Core that helps you manage long-living and distirbuted transactions.
Read more >Getting started - Convey
Welcome to Convey · Chronicle - a simple process manager/saga pattern implementation for .NET Core that helps you manage long-living and distributed transactions ......
Read more >Saga Pattern - Akka-DDD: Process Manager
For example, the creation of an invoice is compensated by its cancellation (see the Ordering Process above). Following this rule, we break the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry for the delay. I’ve been changing the Process doc quite a lot. I tried to make it as good as I can.
Would be great to get some feedback about it. Maybe it’s more readable now?http://eventsourcing.readthedocs.io/en/latest/topics/process.html
Since you were asking about actors, I wanted to say: There’s an incomplete section at the bottom of that doc, about using an actor model framework to orchestrate processing. If you are still interested, perhaps we could work on that together?
I keep returning to the Thespian library, which claims to run actors across a cluster.
It would be great to have a Docker image that can be used in an auto-scaling cluster, something that automatically starts an actor system that runs an event sourced processing system. The actor system could then run the process applications.
Not sure if the Actor system would need to be supervised by e.g. Kubernetes, or if there should be a “leader election” amongst nodes to decide which node runs the Actor system and which nodes follow. If there needs to be a leader election, then perhaps Raft would be sufficient for that?
Basically, it would be great to have something into which people can drop in their aggregates and policies and system definition, and then deploy and have a running, auto-scalable, event-sourced event processing service. It doesn’t have to be the best actor implementation and Docker file ever. But if we could get something working, then we would finally have a spike solution that stretches all the way from event storming, through domain modelling, to a distributed, auto-scaling event processing service.
Hope you’re well.
Very good read. Thanks!
Going to play around with it in bit.