Linux async I/O comparison explains why a TinyGate proxy rewrite moved from epoll to io_uring

The article traces an educational reverse proxy project, TinyGate, from a worker-based design to an epoll implementation and finally a full rewrite around io_uring. It explains that epoll improved performance but still requires extra read/write syscalls after readiness notifications, creating overhead at scale.

The shift from epoll to io_uring reflects a broader Linux networking trend: reducing syscall and context-switch overhead is increasingly central to high-performance server design. For developers building proxies, databases, or event-driven systems, io_uring can offer more headroom but may demand deeper architectural changes.