orb-tokio

Crates.ioorb-tokio
lib.rsorb-tokio
version0.5.0
created_at2025-10-29 09:14:47.214726+00
updated_at2025-11-01 03:54:12.827583+00
descriptionorb interface adaptor for tokio ecology. Orb is an abstraction for writing runtime agnostic async code.
homepage
repositoryhttps://github.com/NaturalIO/orb
max_upload_size
id1906285
size29,270
Adam Ning (frostyplanet)

documentation

https://docs.rs/orb-tokio

README

Orb

Crates.io Documentation

Orb is an abstraction layer for writing runtime-agnostic async Rust code, allowing you to write code that works with different async runtimes, like tokio or smol.

We took the name Orb because it gets around :)

English | 中文

Features

  • Runtime Agnostic: Write code that works with multiple async runtimes
    • The hehavior of this crate is more aligned to tokio, to prevent unnotice bugs (for example, dropping a task handle means detach by default)
  • Extensible: Easy to implement support for new runtimes as plugin, without modification to the main crate.
  • networking:
    • Provide unify abstraction (tcp + unix) as UnifyListener / UnifyStream
    • Non-blocking name resolving: via ResolveAddr trait

The goal

The main goal is to decouple your application logic from specific async runtime implementations, allowing you to:

  • Write portable async code that works at the same time in combination of multiple runtimes

  • Switch to new runtimes without changing your core logic

  • Test your code with different runtime characteristics

  • Enhance async network programing experience

This is a side project during the development of razor-rpc. Because:

  • There is no established standard for designing different runtimes, when developing shared libraries, developers often only target specific runtimes.
  • Using too many #[cfg(feature=xxx)] in code makes it hard to read.
  • Runtimes like smol ecology enable you to customize executors, but there's high learning cost, and lack utility functions (for example, there's no timeout function in async-io or smol).
  • Passing features through sub-projects through multiple layers of cargo dependencies is even more difficult. (that's why we don't use feature in this crate)
  • If users want to customize a runtime for their own needs, they face the dilemma of incomplete ecosystem support.
  • Some projects like Hyper define abstraction layers, having each project do this individually is a huge maintenance cost.

This is why this crate was written.

Usage

To use Orb, you need to depend on both the core orb crate and a runtime adapter crate like orb-tokio or orb-smol.

In your Cargo.toml:

[dependencies]
# when you write runtime agnostic codes
orb = "0"
# when you setup as end-user
orb-tokio = "0"
# or
orb-smol = "0"

There's a global trait AsyncRuntime that combines all features at the crate level, and adding use orb::prelude::* will import all the traits you need.

There are some variants of the new() function, also refer to the documentation in the sub-crates:

License

This project is licensed under the MIT License - see the LICENSE file for details.

Commit count: 0

cargo fmt