I’ve been experimenting with building a Node.js HTTP framework using Rust + Hyper with N-Api.

The project started as a fully synchronous server, but I recently patched it to support async (Tokio/Hyper). That change alone nearly doubled throughput in benchmarks.

What’s different:

* Built directly on Hyper, no heavy abstraction * napi glue for Node.js bindings * Minimal core (sync and async engines side-by-side) * Focused on raw performance, not plugins (yet)

This is still experimental and not production-ready. I’d like feedback on:

* Async API design — does it feel ergonomic? * Middleware style — what patterns should be supported?

Repo: [https://github.com/Shyam20001/rsjs](https://github.com/Shyam20001/rsjs) Full benchmarks: [https://shyam20001.github.io/rsjs/](https://shyam20001.github.io/rsjs/)