Roger Johansson

Port OpenTelemetry Tracing

1

Currently, we have OpenTracing support in Proto.Actor Go. OpenTracing is however obsolete in favor of OpenTelemetry. We could use this code as a base for creating the new OpenTelemetry tracing

Port Client connections

1

This is a pretty major feature. will collect info here on what tasks needs to be done

Port Gracefully Left

1

https://github.com/asynkron/protoactor-dotnet/blob/dev/src/Proto.Cluster/Gossip/Gossiper.cs#L167

https://github.com/asynkron/protoactor-dotnet/blob/e792c805baf29a50af2a1bd665e2a21ded7662f3/src/Proto.Cluster/Gossip/Gossiper.cs#L183

Port BatchFutures and co.

1

https://github.com/asynkron/protoactor-dotnet/blob/dev/src/Proto.Actor/Future/FutureBatch.cs FutureBatch is a special Future that registers into the ProcessRegistry, and then allows requests to re-use this future but with a unique request-id per request.

https://github.com/asynkron/protoactor-dotnet/blob/dev/src/Proto.Cluster/Gossip/Gossiper.cs#L167

Now that gossip is enabled, we should use the consensus features inside the identity lookups in the same way as we do in .NET This allows the cluster to better...

Currently we are running with half the Gossip only. e.g. Member A sends gossip to member B Member B acks "OK" The full flow should be Member A sends gossip...

With the gossip protocol, we can now easily do seed node based cluster membership. We should port this over from .NET https://github.com/asynkron/protoactor-dotnet/tree/dev/src/Proto.Cluster/Seed

Proto.Actor .NET has a Cluster PubSub feature. this should exist for Go also