Rust implementation of Dataspaces, Syndicate, and a high-speed networked dataspace broker.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tony Garnock-Jones bc5e4fa736 (cargo-release) syndicate version 0.9.1 3 months ago
dev-scripts dev-scripts 4 months ago
syndicate (cargo-release) version 0.9.1 3 months ago
syndicate-macros (cargo-release) version 0.4.1 3 months ago
syndicate-server (cargo-release) syndicate version 0.9.1 3 months ago
.gitignore Use OUT_DIR 4 months ago
Cargo.lock (cargo-release) syndicate version 0.9.1 3 months ago
Cargo.toml Strip release binaries 3 months ago
Makefile Move cross build stuff to root Makefile/root package 3 months ago Split out syndicate-server crate 4 months ago
rust-toolchain Split out syndicate-server crate 4 months ago
syndicate-rs-server.png 7 months ago


A Rust implementation of:

  • the Syndicated Actor model (partial; includes assertion-based communication, failure-handling, capability-style security, and dataspace entities, but not (yet) facets as a structuring principle);

  • the Syndicate network protocol, including

    • a high-speed Dataspace indexing structure (; see also from syndicate-rkt) and

    • a standalone Syndicate protocol "broker" service (roughly comparable in scope and intent to D-Bus); and

  • a handful of example programs.

The Syndicate/rs server running.
The Syndicate/rs server running.


git clone
cd syndicate-rs
cargo build --release

Running the examples

In one window, start the server:


Then, choose one of the examples below.

Producer/Consumer (sending messages)

In a second window, run a "consumer" process:


Finally, in a third window, run a "producer" process:


State producer/consumer (state replication)

Replace producer with state-producer and consumer with state-consumer, respectively, in the instructions of the previous subsection to demonstrate Syndicate state replication.

Pingpong example (latency)

In a second window, run

./target/release/examples/pingpong pong

and in a third window, run

./target/release/examples/pingpong ping

The order is important - the difference between ping and pong is about who kicks off the pingpong session.

Performance note

You may find better performance by restricting the server to fewer cores than you have available. For example, for me, running

taskset -c 0,1 ./target/release/syndicate-server

roughly quadruples throughput for a single producer/consumer pair, on my 48-core AMD CPU.