Ergo: Erlang-inspired event driven actor framework in Go

What kind of practical, real-word problems can I solve with this, as a backend engineer at a hedge fund? Im struggling to understand why I even need actor frameworks when my processes are already supervised, pretty much never crash, and all communicate over gRPC and Kafka? Not trying to be snarky, just don’t understand how this paradigm could assist me.

For more context, most of my work is around real-time streaming / monitoring of trades and trading metrics.

You are probably thinking too course-grained. Erlang-style actors are closer to functions than processes.

For example you could parallelize a for loop by creating a goroutine for each item in a list. Or separate actors for logging, session tracking, connection pools, etc.

Doing that with processes and Kafka would be massive overhead.