Why ZON?
In high-frequency trading (HFT) and multiplayer gaming, latency is the enemy. Traditional formats like JSON and Protobuf introduce a hidden tax: parsing. Every time you read a message, your CPU burns cycles checking syntax, allocating strings, and decoding schemas. ZON eliminates this tax. It maps files directly to memory. By using pointer-less relative offsets and strict 64-byte alignment (cache-line friendly), the on-disk format is the in-memory representation.The 3 Core Pillars
Zero-Copy
Data is read directly from the buffer. No parsing. No allocation. No GC pressure.
Schema-Less
Self-describing binary format. No
.proto files to compile or manage.WASM-Native
Built for the web. Bridges Rust performance to Node.js and Browser environments.
Performance at a Glance
Benchmarks vs. JSON for a standard Game Entity:| Metric | JSON | ZON | Improvement |
|---|---|---|---|
| Access Time | ~117.43 ns | ~18.83 ns | 6.2x Faster |
| Throughput | ~8.5 M ops/s | ~53.1 M ops/s | 6.2x Higher |