Absolutely, Inlining per question here:
Starting in reverse order:
How does Asynkron fit into the picture? What is your revenue model and relationship to proto.actor as an open-source project?
I’m the founder of Asynkron and the Proto.Actor project.
Asynkron as a company is the owner of the Proto.Actor trademark.
The opensource projects are also under a Contributors License Agreement, which grants Asynkron the signed license to use the contributed code.
Under Asynkron, we offer consulting services around scalability, distributed systems, workshops, training sessions around the actor model in general, and Proto.Actor as a framework, e.g. helping clients architect and implement Proto.Actor systems.
We are currently in negotiations with a potential partner company for setting up a full set of support plans for Proto.Actor.
Offering developer support and full-fledged 24/7 SLA production support.
How are they related, i.e. kept in sync functionality / compatibility wise? Is Golang part of the long-term roadmap of proto.actor as something with prolonged commitment / support?
The plan is to keep the two fully in sync. currently working on porting over all the new cluster features from .NET to Go.
Which project gets the most attention depends very much on where there currently are the most contributors, and what clients we are working with. e.g. I am working full time with a .NET customer right now, which leads to more progress on the .NET version.
Personally, I do believe Proto.Actor Go has a brighter future as Go generally is more used in the high-scalability world.
Hope this sheds some light on your questions?
Let me know if there is anything that I can elaborate on