It seems title is wrong. It should be "my actor framework in Rust" because you didn't distill transferable lessons. In fact there's lots that could be better - unnecessary dispatch (dyn Any and linear string search when all non-skipped messages are known at compile time), unnecessary latency (waiting for future data rather than windowing over the past like gzip), unnecessary reimplementation of tcp (just stop consuming from the kernel and it will backpressure), unnecessary use of tcp (each connection needs a tcp and maybe encryption handshake, adding a lot of first-message latency, which is _most_ messages when you scale up). None of this is critical, but it's what would make it 'fast and efficient' beyond just solving the problem
It seems title is wrong. It should be "my actor framework in Rust" because you didn't distill transferable lessons. In fact there's lots that could be better - unnecessary dispatch (dyn Any and linear string search when all non-skipped messages are known at compile time), unnecessary latency (waiting for future data rather than windowing over the past like gzip), unnecessary reimplementation of tcp (just stop consuming from the kernel and it will backpressure), unnecessary use of tcp (each connection needs a tcp and maybe encryption handshake, adding a lot of first-message latency, which is _most_ messages when you scale up). None of this is critical, but it's what would make it 'fast and efficient' beyond just solving the problem
it seems title is wrong. It should be " Fast and efficient network protocols in Rust" by Nikita Lapkov