data-signals 0.1.0

Umbrella crate for the live-data ecosystem: protocol types (live-data), publisher SDK (live-feed), consumer SDK (live-stream).
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

# data-signals

Parent crate and workspace for the **live-data** ecosystem: a
unified, transport-agnostic stack for publishing and consuming live
data feeds backed by SIMD-aligned columnar memory.

## Crates in this workspace

| Crate | Role |
|-------|------|
| [`live-data`](live-data/) | Protocol types: descriptors, manifests, subscriptions, schema. |
| [`live-feed`](live-feed/) | Publisher SDK: declare feeds, build manifests, serve subscribers. |
| [`live-stream`](live-stream/) | Consumer SDK: browse manifests, open subscriptions, receive batches. |

The umbrella `data-signals` crate at the workspace root pulls these in
via Cargo features, so applications can write a single dep line and
opt into the publisher and/or consumer side:

```toml
data-signals = "0.1"                                  # protocol types only
data-signals = { version = "0.1", features = ["publisher"] }
data-signals = { version = "0.1", features = ["consumer"] }
data-signals = { version = "0.1", features = ["all"] }
```

Connector crates (e.g. `live-binance`) live in the sibling
[`live-connectors`](https://github.com/pbower/live-connectors)
workspace and depend on `live-data` plus the underlying transport
layer.

## Status

Early development, API in flux. The 0.1.0 line locks the wire
protocol shape; runtime SDKs flesh out in 0.2.x.

## License

Mozilla Public License 2.0 (MPL-2.0). See [LICENSE](LICENSE).