transitions VS protoactor-go

Start with that you know, if you know Excel well, why not start there? I usually recommend Python if you’re new to programming, then you can pick whatever additional libraries you think would benefit the model, and the syntax is highly forgiving. Sounds to me like you’re describing a pretty big finite state machine, with 288 states. Once you encode your idea and some tests, you’ll have the vocabulary (and means) to expand to other model variations such as applying probabilities to different transition states, and opening a whole world of probabilistic models and hidden Markov models, but gotta walk before running :)

BTW, did you check this?

https://github.com/pytransitions/transitions/blob/master/exa...

Transitions

In Python's ecosystem of libraries, there's a nice one called transitions (which I've used in my robotics work). transitions (as the name suggests) lets you define your state machines more declaratively in terms of transitions between states, the rules that govern those transitions, and the triggers that cause these transitions to happen.

https://github.com/asynkron/protoactor-go & this is a great lib, that implements a Erlang/Akka-like the Actor Model in Go.

I have worked with Orleans and Orbit a little bit and always wanted to have a look to akka.net or proto.actor. Do you know an Open Source project which makes use of actors?

Looks cool. However, since this is a paid product… if one wants an actor framework for go without the need to connect to Erlang nodes, this will be a fine choice: https://github.com/asynkron/protoactor-go.

A used this a couple of times in production: https://github.com/asynkron/protoactor-go.

No problem launching a 100k actors on a laptop.

https://proto.actor is pretty brand new and uses gRPC

This would be my go to for anything _supervisor_ in golang: https://github.com/asynkron/protoactor-go#supervision.