ntex is part of an Ecosystem of Crates

ntex is a framework for composable network services.

We call ntex a powerful and pragmatic framework. For all intents and purposes it's a micro-framework with a few twists. If you are already a Rust programmer you will probably find yourself at home quickly, but even if you are coming from another programming language you should find ntex easy to pick up.

An application developed with ntex will expose an HTTP server contained within a native executable. You can either put this behind another HTTP server like nginx or serve it up as-is. Even in the complete absence of another HTTP server ntex is powerful enough to provide HTTP/1 and HTTP/2 support as well as TLS (HTTPS). This makes it useful for building small services ready for production.

ntex have several other implementations such as:

• ntex-grpc A GRPC Client/Server framework
• ntex-redis A redis client
• ntex-mqtt A MQTT Client/Server framework for v5 and v3.1.1 protocols

ntex has a native single-threaded runtime. Without an explicit runtime feature it automatically selects a platform I/O reactor: Linux tries io_uring and falls back to polling, other Unix platforms use polling, and Windows uses IOCP. Alternative runtimes and native reactors can be selected with Cargo features (enable at most one):

• tokio: Tokio local runtime and I/O driver.
• compio: Compio runtime with completion-based I/O.
• neon-polling: native runtime with the polling reactor on Unix.
• neon-uring: native runtime with io_uring on Linux.

Most importantly: ntex runs on Rust 1.97 or later and it works with stable releases.