Broker - Real-time Zero-Code API Server

Purpose

The purpose of this library is to be your real-time zero-code API server.

Broker is a SSE message broker that requires you write no backend code to have a full real-time API.

Broker is born from the need that rather than building a complex REST API with web-sockets and a SQL database to provide reactive web forms (like for React) 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 create a user, login, then insert an event with its data, a collectionid, and a timestamp. Broker publishes the event when the timestamp is reached to the event stream via SSE. Broker keeps all events its database that can be viewed in collections (by collectionid). Broker can also cancel future events.

When the client first subscribes to the SSE connection all the latest events and data is sent to the client. Combined with sending the latest event via SSE when subscribed negates the 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.

API

this library is 1.0.0 and the API is stable

Step 1 - create a user

html POST /users - public endpoint - POST JSON to create a user json {"username":{...}, "password":{...}, "collection_id":{...}} - where {...} is for username and string, password a string, and collection_id is the uuid of the event collection for user info

will return json {"id":{...}} - where {...} is the uuid (string) of the user

Step 2 - login with the user

html POST /login - public endpoint - POST JSON to login json {"username":{...}, "password":{...}} - where {...} is for username a string and password a string

will return json {"jwt":{...}} - where {...} is a JWT (string)

Step 3 - insert an event

html GET /events - public endpoint - connect your sse-client to this endpoint

html POST /insert - authenticated endpoint (Authorization: Bearer {jwt}) - POST JSON to insert an event json {"event":{...}, "collection_id":{...}, "timestamp":{...}, "data":{...}} - where {...} is for the event a string, collection_id is an assigned uuid v4 for the event collection, timestamp is the epoch unix timestamp when you want the event to become the current event, and data is any JSON you want

will return json {"id":{...}} - where {...} is the uuid (string) of the event

Optional Endpoints

html GET /events/collections/{collection_id} - authenticated endpoint (Authorization: Bearer {jwt}) - do a GET request where {collection_id} is the uuid of the collection you want (sorted by ascending timestamp)

html GET /events/user - authenticated endpoint (Authorization: Bearer {jwt}) - do a GET request to get the user event collections (sorted by ascending timestamp)

will return json {"info": {...}, "events":{...}} - where (...) is for info a list of events for user info and events a list of all events that the user inserted

html GET /events/{id}/cancel - authenticated endpoint (Authorization: Bearer {jwt}) - do a GET request where id is the uuid of the event to cancel a future event

Features

Very performant with a low memory footprint
Real-time Event Stream via SSE
CORS support
Handles SSE client timeouts
Provides user authentication with JWTs and Bcrypt(ed) passwords
Handles future events via Epoch UNIX timestamp
Stateful immutable event persistence
Insert event via JSON POST request
Sync latest events on SSE client connection
Event log via GET request
Event cancellation via GET request

Use

```rust use broker::{broker_run};

[actix_rt::main]

async fn main() -> std::result::Result<(), std::io::Error> { brokerrun("http://localhost:3000".toowned()).await } ```

the only param is the origin you want to allow - wildcard is not supported
the PORT needs to be passed in as an environment variable
the EXPIRY (for jwts) needs to be passed in as an environment variable
the SECRET (for jwts) needs to be passed in as an environment variable
the SAVE_PATH where the embedded database will save needs to be passed in as an environment variable