boardwalk

A hypermedia server framework for federated services. Boardwalk models things as state machines, exposes them as discoverable Siren resources over HTTP, multiplexes telemetry over WebSockets, and tunnels HTTP requests back through outbound peer connections so services behind a NAT stay reachable from anywhere else on your fleet.

Boardwalk started as a Rust port of Zetta and is evolving independently from there.

Install

[dependencies]
boardwalk = "0.1"
tokio = { version = "1", features = ["full"] }

Quick start

use boardwalk::{Boardwalk, Device, DeviceConfig, DeviceError, TransitionInput};
use futures::future::BoxFuture;

#[derive(Default)]
struct Led { on: bool }

impl Device for Led {
    fn config(&self, cfg: &mut DeviceConfig) {
        cfg.type_("led")
            .state(self.state())
            .when("off", &["turn-on"])
            .when("on", &["turn-off"])
            .monitor("state");
    }
    fn state(&self) -> &str { if self.on { "on" } else { "off" } }
    fn transition<'a>(
        &'a mut self,
        name: &'a str,
        _input: TransitionInput,
    ) -> BoxFuture<'a, Result<(), DeviceError>> {
        Box::pin(async move {
            match name {
                "turn-on"  => { self.on = true;  Ok(()) }
                "turn-off" => { self.on = false; Ok(()) }
                other      => Err(DeviceError::Invalid(other.into())),
            }
        })
    }
}

#[tokio::main]
async fn main() -> anyhow::Result<()> {
    Boardwalk::new()
        .name("hub")
        .use_device(Led::default())
        .listen("127.0.0.1:1337".parse()?)
        .await
}

curl http://127.0.0.1:1337/servers/hub
DEV=$(curl -s http://127.0.0.1:1337/servers/hub | jq -r '.entities[0].properties.id')
curl -d 'action=turn-on' http://127.0.0.1:1337/servers/hub/devices/$DEV

What's in the box

• Devices as state machines — typed Device trait with allowed transitions per state, input fields, monitored properties.
• Siren hypermedia API — root, server, device, type metadata, and search-result resources, with cross-server peer links.
• Multiplex WebSocket events at /events — subscribe to topics with * / ** / regex patterns, optional CaQL filters.
• CaQL — small query DSL for selecting and projecting devices.
• Peer tunnel — hub dials cloud via an outbound WebSocket; both sides upgrade to HTTP/2 with reversed roles. The cloud then proxies HTTP and forwards event subscriptions back through the same socket.
• TLS — peer dials use rustls + the OS trust store via rustls-platform-verifier.
• Persistence — opt-in via Boardwalk::persist(path). Stable device IDs across restarts, peer record persistence.

Run the example

cargo run --bin hello-led

There's also a tunnel proof-of-concept that drives role-reversed HTTP/2 over an arbitrary duplex stream:

cargo run --bin tunnel-poc

Crate layout

The published API surface is the boardwalk facade. Everything else is split across narrowly-scoped crates so driver authors and embedders can pick what they need:

Docs

• Getting started — install, write a driver, run the server, talk to it.
• Devices — Device trait, properties, streams, scouts, persistence.
• Peers — reverse-tunnel hub ↔ cloud setup.
• CaQL — query DSL reference.

License

Apache-2.0. See LICENSE.