You can see the benchmarks for the network messaging here https://github.com/ergo-services/benchmarks

On CPU with 64 cores it demonstrates almost 5M msg/sec over the network (64 processes are sending message to another 64 processes on the second node) https://x.com/halturin/status/1831820525292880033

For the Erlang stack I published my results here https://x.com/halturin/status/1802801540216054040

Anyway, performance is heavily depends on the specific case and nature of the data.

PS before you start to desing your solution it would be better to read the documentation https://docs.ergo.services/networking/network-stack

I have reviewed the documentation, but I am not currently using a service discovery program like EPMD. Instead, I have implemented ETCD as an additional service discovery mechanism. When a new service registers, I use Node.Network().GetNode to connect to the new node. In this case, if I have many new nodes (for example, hundreds) connecting to the current node simultaneously, could there be issues? Do I have any optimization solutions?

dont see any problem with it. if you get some, feel free to report.

PS would be great to see your ETCD implementation open-sourced. if it is applicable to the general use case I can add it to the extra library (github.com/ergo-services/registrar).

dont see any problem with it. if you get some, feel free to report.

PS would be great to see your ETCD implementation open-sourced. if it is applicable to the general use case I can add it to the extra library (github.com/ergo-services/registrar).

I will try to implement it. Thank you very much for your reply!