Rust implementation of Dataspaces, Syndicate, and a high-speed networked dataspace broker.
Go to file
Tony Garnock-Jones 4e46d4a381 make pull-protocols 2021-07-01 10:01:19 +02:00
benches Benchmarks of internal routing fabric 2020-06-17 13:42:33 +02:00
examples Variable-sized padding for examples 2020-06-15 22:13:21 +02:00
protocols/schemas Add 'protocols/' from commit '93c196acaaf85e406f579a94489af5f1ade04ebd' 2021-07-01 10:00:50 +02:00
src Update URL 2021-05-07 17:09:38 +02:00
.gitignore Cargo.lock from last time I had this building and running 2020-05-06 14:53:54 +02:00
Cargo.lock Bump deps (including preserves) 2021-05-17 16:38:40 +02:00
Cargo.toml Bump deps (including preserves) 2021-05-17 16:38:40 +02:00
Makefile make pull-protocols 2021-07-01 10:01:19 +02:00
README.md README.md 2021-05-12 15:36:27 +02:00
rust-toolchain Tokio-0.2 based Preserves chat-ish server 2019-09-24 22:07:49 +01:00
syndicate-rs-server.png README.md 2021-05-12 15:36:27 +02:00

README.md

Syndicate/rs

A Rust implementation of:

  • the Syndicate network protocol, including
  • a high-speed Dataspace indexing structure (see HOWITWORKS.md from syndicate-rkt),
  • a standalone Syndicate protocol broker service, and
  • a handful of examples.

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

Quickstart

git clone https://git.syndicate-lang.org/syndicate-lang/syndicate-rs
cd syndicate-rs
cargo build --release
./target/release/syndicate-server

Running the examples

In one window, start the server:

./target/release/syndicate-server

Then, choose one of the examples below.

Producer/Consumer (sending messages)

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

./target/release/examples/consumer

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

./target/release/examples/producer

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.