broker 0.2.1

SSE Real-time Message Broker
Documentation
broker-0.2.1 has been yanked.

Broker - SSE Real-time Message Broker

crates.io

Purpose

The purpose of this library is to provide a SSE real-time message broker.

Broker is born from the need that rather than building a complex REST API with web-sockets to provide reactive web forms there must be a simpler way.

Broker follows an insert-only/publish/subscribe paradigm rather than a REST CRUD paradigm.

How it works

In Broker you insert an event and its data via a JSON POST request (/insert). Broker publishes the latest event to an event stream via SSE (/events) and keeps all versions in its database that can be viewed in a JSON GET request (/audit/{event}).

When the client first subscribes to the SSE connection (/events) all the latest events and data is sent to the client. Combined with sending the latest event via SSE when subscribed negates any necessity to do any GET API requests in the lifecycle of an event.

The side-effect of this system is that the latest event is the schema. Old events are saved in the database and are not changed but the latest event is the schema for the front-end. This is pure NoSQL as the backend is agnostic to the event data.

Features

  • Real-time Event Stream via SSE
  • CORS support
  • Handles SSE client timeouts
  • Stateful immutable event persistence
  • JSON POST API to insert events
  • Sync latest events on SSE client connection
  • Audit log of events
  • Very performant with low memory footprint

Use

use broker::{broker_run};

#[actix_rt::main]
async fn main() -> std::result::Result<(), std::io::Error> {
    broker_run("*".to_owned()).await
}
  • the only param is the origin you want to allow - wildcard for all
  • the PORT needs to passed in as an environment variable

Endpoints

/events

  • connect your sse-client to this endpoint

/insert

  • POST JSON to insert an event
{"event":{...}, "data":{...}}
  • where {...} is for the event a string and data is any JSON you want

/audit/{event}

  • do a GET request where {event} is the name of the event you want the audit log
  • the audit log will be {event}_v_{timestamp} as the key with the data as a value

View Example

Run Example

  • make
  • make client

Demo

Inspiration