Automatonymous
Stateless
Our great sponsors
| Automatonymous | Stateless | |
|---|---|---|
| - | 9 | |
| 727 | 5,292 | |
| 0.8% | 1.0% | |
| 0.0 | 6.9 | |
| over 1 year ago | 14 days ago | |
| C# | C# | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Automatonymous
We haven't tracked posts mentioning Automatonymous yet.
Tracking mentions began in Dec 2020.
Stateless
- Validating model based on Rules
-
Best practices for managing menu items that need to be enabled/disabled?
I like this method and state machines in general. Makes it more easier to reason about complex software. Also, ithe f the state machine gets bigger (more states) in the past I have used the Stateless library which is very good. But what you described above is perfect for managing the state of a menu system.
-
Architecture pattern for Console Apps?
After using stateless for three years, my conclusion is that I cannot imagine a scenario, where it makes sense to use it.
-
Modelling workflows with Finite State Machines in .NET
This is a great article. Here is the Stateless library he is writing about. The link to the library is kind of buried in the middle of a sentence.
- How to create event tree c#
-
Which service should store which data in a microservice architecture?
Yes! And we're using one. https://github.com/dotnet-state-machine/stateless We're creating the configuration dynamically based on how the user wants his workflow to work.
-
Need Finite-State Machine framework for TCP socket clients
Stateless is my go-to state machine library for .NET. It's reasonably advanced but can also be very simple if you don't need the more advanced features.
-
Has UML died without anyone noticing?
I'm playing around with this library for a medium sized state machine I'm setting up, and it has this functionality. I think explicit state machines are a good use-case for having an actual diagram, since they can take up enough space that it becomes hard to build a mental map from reading the code due to locality issues.
What are some alternatives?
Appccelerate - State Machine - A .net library that lets you build state machines (hierarchical, async with fluent definition syntax and reporting capabilities).
LiquidState - Efficient asynchronous and synchronous state machines for .NET
MassTransit - Distributed Application Framework for .NET
coyote - Coyote is a library and tool for testing concurrent C# code and deterministically reproducing bugs.
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
Sprache - A tiny, friendly, C# parser construction library
command-line-api - Command line parsing, invocation, and rendering of terminal output.
tplant - Typescript to plantuml
Gui.cs - Cross Platform Terminal UI toolkit for .NET