3 unstable releases

0.9.1 Sep 10, 2021
0.9.0 Sep 7, 2021
0.8.0 Jun 29, 2021

22 downloads per month
Used in 3 crates

MIT license

13K SLoC

What is netidx?

  • It's a directory service; like LDAP or X.500

    • It keeps track of a hierarchical directory of things
    • It's browsable and queryable
    • It's distributed, lightweight, and scalable
  • It's a tuple space; like JavaSpaces, zookeeper, or memcached

    • Except it's distributed. The directory server keeps track of where things are, publishers keep the data.
    • Each tuple is identified by a unique path in the directory server, and holds a flexible set of primitive data types
  • It's a publish/subscribe messaging system; like MQTT

    • Except there is no centralized broker. Communication happens directly between publishers and subscribers
    • Message archiving and other services provided by MQTT brokers can be provided by normal publishers, or omitted if they aren't needed
    • Decentralization allows it to scale to huge message rates

For more details see the netidx book

Here is an example service that publishes a cpu temperature, along with the corresponding subscriber that consumes the data.


use netidx::{
    publisher::{Publisher, Value, BindCfg},
use tokio::time;
use std::time::Duration;
use anyhow::Result;

fn get_cpu_temp() -> f32 { 42. }

async fn run() -> Result<()> {
    // load the site cluster config. You can also just use a file.
    let cfg = Config::load_default()?;

    // no authentication (kerberos v5 is the other option)
    // listen on any unique address matching
    let publisher = Publisher::new(cfg, Auth::Anonymous, "".parse()?).await?;

    let temp = publisher.publish(

    loop {
        let mut batch = publisher.start_batch();
        temp.update(&mut batch, Value::F32(get_cpu_temp()));


use netidx::{
    subscriber::{Subscriber, UpdatesFlags},
use futures::{prelude::*, channel::mpsc};
use anyhow::Result;

async fn run() -> Result<()> {
    let cfg = Config::load_default()?;
    let subscriber = Subscriber::new(cfg, Auth::Anonymous)?;
    let path = Path::from("/hw/washu-chan/cpu-temp");
    let temp = subscriber.subscribe_one(path, None).await?;
    println!("washu-chan cpu temp is: {:?}", temp.last());

    let (tx, mut rx) = mpsc::channel(10);
    temp.updates(UpdatesFlags::empty(), tx);
    while let Some(mut batch) = rx.next().await {
        for (_, v) in batch.drain(..) {
            println!("washu-chan cpu temp is: {:?}", v);

Published things always have a value, which new subscribers receive initially. Thereafter a subscription is a lossless ordered stream, just like a tcp connection, except that instead of bytes publisher::Value is the unit of transmission. Since the subscriber can write values back to the publisher, the connection is bidirectional, also like a Tcp stream.

Values include many useful primitives, including zero copy bytes buffers (using the awesome bytes crate), so you can easily use netidx to efficiently send any kind of message you like. However it's advised to stick to primitives and express structure with multiple published values in a hierarchy, since this makes your system more discoverable, and is also quite efficient.

netidx includes optional support for kerberos v5 (including Active Directory). If enabled, all components will do mutual authentication between the resolver, subscriber, and publisher as well as encryption of all data on the wire.

In krb5 mode the resolver server maintains and enforces a set of authorization permissions for the entire namespace. The system administrator can centrally enforce who can publish where, and who can subscribe to what.


~226K SLoC