Late to the party, but... The Distributed Job System I've written for .NET [1] uses Akka.NET under the hood. Mind you, this runs 'distributed' in the sense th

Late to the party, but... The Distributed Job System I've written for .NET [1] uses Akka.NET under the hood. Mind you, this runs 'distributed' in the sense that you can have multiple servers; the actors in the Execution System itself don't do anything outside of process. However, they are very much written in the actor spirit. There's only 3 Actors, but that might fit the bill for being something that's not 'hello world' but not huge. The entire system is about 4KLOC, And the Actor part of the system is under 1KLOC including the Class that manages the ActorSystem at runtime. The unmerged branch has some even more advanced examples around recovery as well as a more 'pure' model around the Coordinator (In /master/ there is still a blocking call to the Queue.) [1] https://github.com/to11mtm/oddjob https://github.com/to11mtm/oddjob