Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
So so many better ways, one of the most modern is io_uring which allows you to (if you choose for the complexity involved) set up receive pools and buffers per core (or thread), and have effectively a zero-sys-call async runtime. Reality though currently is that it is really hard and outside of specific hot-path stuff (nginx for example) true zero syscall is a bit away. DotNet CLR itself has core problems of how different of an API it is that it is still a tracked feature request. The closest on windows is IO Completion Ports, but those are also maddening to use and setup correctly. (In my opinion, even more maddening than io_uring, but that may be my bias on being able to read Linux kernel code to sus things out). The CLR on windows (both Framework and Core) does not use IOCP unless explicitly used.