dev/content/docs/ecosystem.mdx at main

zap-proto/dev

Fork 0

mirror of https://github.com/zap-proto/dev.git synced 2026-10-30 15:05:18 +00:00

Files

T

6f0dfd20c5 docs: complete tooling story (pb2zap + zap2pb), zip server, ZAP-only production case (#1 )

* docs: tools section (pb2zap, zap2pb), zip server page, ZAP-only production story

- content/docs/tools/: new Tooling nav group — the complete pb<->ZAP
  interop boundary. pb2zap (go/ast codemod off protobuf), zap2pb
  (the one sanctioned protobuf import: Marshal/Unmarshal/Equal/
  AppendMessage, v0.2.0), and the migration path over the existing
  schema/codegen pages.
- content/docs/zip.mdx: the ZAP-native application server — one
  Listen verb (ZAP primary, HTTP secondary), typed handlers with
  REST/OpenAPI/MCP projections, Mount composition, and the
  hanzoai/cloud case: sub-1,000-line compose root hosting ~75K LOC
  of subsystems (76:1).
- why-zap: scrub the unmeasured benchmark tables (per the
  benchmarks-page policy), replace with mechanism arguments and the
  ZAP-only-in-production account: zero gRPC, protobuf confined to
  the four-function zap2pb boundary at the OTLP edge.
- ecosystem: add zip/pb2zap/zap2pb rows; quick-start + index: link
  the new pages, drop the unmeasured 5-20x claim.

* fix(build): alias MDX collections to regenerated docs/, drop frozen .docs snapshot

next.config.mjs and tsconfig.json pointed @hanzo/docs-mdx:collections/*
at .docs/ — a snapshot frozen on Jun 1 — while the MDX plugin
regenerates docs/ on every build. Result: no page added since the
snapshot (schema, codegen, rpc, capabilities, and this PR%27s tools/zip)
was ever emitted; the site silently served 37 routes instead of 45.
Alias both resolvers at docs/ and remove .docs.

---------

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-07 17:58:42 -07:00

76 lines

4.5 KiB

Plaintext

Raw Permalink Blame History

 ---
 title: Ecosystem
 description: Open-source services using ZAP — production users, libraries, and demos.
 ---
 # Ecosystem
 Open-source services that depend on ZAP directly. The list below is grepped from public `go.mod` / `Cargo.toml` / `package.json` files and verified to actually link ZAP packages (not just mention them in docs).
 ## Native ZAP RPC
 Services that use `github.com/zap-proto/go` directly as their application protocol.
 | Service | Repo | Role |
 |---|---|---|
 | **Hanzo PubSub** | [hanzoai/pubsub](https://github.com/hanzoai/pubsub) | Native ZAP RPC for the pubsub control plane; payload framing on the data plane |
 | **Hanzo Storage** | [hanzoai/storage](https://github.com/hanzoai/storage) | Native RPC between storage shards; capability-passing for cross-shard reads |
 | **Hanzo Tasks** | [hanzoai/tasks](https://github.com/hanzoai/tasks) | Native RPC between scheduler ↔ worker pool; task handles are ZAP capabilities |
 | **Hanzo Playground** | [hanzoai/playground](https://github.com/hanzoai/playground) | Sandboxed runner ↔ host control surface |
 | **Hanzo Base-HA** | [hanzoai/base-ha](https://github.com/hanzoai/base-ha) | Cross-replica state-machine replication |
 ## HTTP over ZAP
 Services using [`zap-proto/http`](https://github.com/zap-proto/http) — the `net/http` drop-in.
 | Service | Repo | Role |
 |---|---|---|
 | **Hanzo Gateway** | [hanzoai/gateway](https://github.com/hanzoai/gateway) | API gateway terminating user HTTP, proxying upstream over ZAP-HTTP |
 | **Hanzo Ingress** | [hanzoai/ingress](https://github.com/hanzoai/ingress) | L7 reverse proxy, serves ZAP-HTTP on the cluster-internal hop |
 | **Hanzo Cloud** | [hanzoai/cloud](https://github.com/hanzoai/cloud) | Unified control plane — one binary, 15+ subsystems on a sub-1,000-line [zip](/docs/zip) compose root, zero gRPC/protobuf in app code |
 | **Lux ZAP** | [luxfi/zap](https://github.com/luxfi/zap) | Lux-network reference integration |
 ## Libraries & tooling
 | Project | Repo | Description |
 |---|---|---|
 | **zip** | [zap-proto/zip](https://github.com/zap-proto/zip) | [ZAP-native application server](/docs/zip) — Fiber v3/fasthttp core, ZAP primary + HTTP secondary, one Listen verb |
 | **pb2zap** | [zap-proto/pb2zap](https://github.com/zap-proto/pb2zap) | [`go/ast` codemod](/docs/tools/pb2zap) migrating protobuf construction sites to ZAP wire constructors |
 | **zap2pb** | [zap-proto/zap2pb](https://github.com/zap-proto/zap2pb) | [The sanctioned ZAP↔protobuf wire boundary](/docs/tools/zap2pb) — one file, four functions |
 | **Hanzo zap-es** | [hanzoai/zap-es](https://github.com/hanzoai/zap-es) (mirror of [zap-proto/zap-es](https://github.com/zap-proto/zap-es)) | Cap'n-Proto-style wire encoder for TypeScript |
 | **Hanzo Marketing** | [hanzoai/marketing](https://github.com/hanzoai/marketing) | Static-site build pipeline (uses ZAP-HTTP for the rebuild trigger hook) |
 ## Reference implementations
 These are the canonical SDKs themselves — listed because they're also OSS services in their own right:
 | Package | Repo |
 |---|---|
 | Go reference | [zap-proto/go](https://github.com/zap-proto/go) |
 | Rust reference | [zap-proto/rust](https://github.com/zap-proto/rust) |
 | TypeScript | [zap-proto/ts](https://github.com/zap-proto/ts) |
 | Python | [zap-proto/py](https://github.com/zap-proto/py) |
 | C++ | [zap-proto/cpp](https://github.com/zap-proto/cpp) |
 | All others | [github.com/zap-proto](https://github.com/zap-proto) (33 repos) |
 ## Adding your service
 If you're shipping a public service or library that links ZAP packages, open a PR against [zap-proto/dev](https://github.com/zap-proto/dev) — single line in this ecosystem page. We don't gatekeep; we just want a public repo + a real `go.mod` / `Cargo.toml` / `package.json` entry.
 Production but private deployments are tracked separately under the case-studies workstream — reach out at [email protected].
 ## Performance reference points
 These deployments share their numbers on the [benchmarks page](/docs/benchmarks):
 - **Hanzo Gateway** — 1.1M req/s per gateway pod (8 cores), p99 < 200 µs at the edge
 - **Hanzo PubSub** — 1.8M msg/s per broker, 22 µs p99 fan-out latency
 - **Hanzo Tasks** — task-handle capability passing across 10k concurrent workers, no serializer hot spot
 ## Related
 - [SDKs](/docs/sdks) — pick your language and start shipping
 - [Protocols](/docs/protocols) — native ZAP vs. carrier protocols
 - [Tools](/docs/tools) — codegen and the protobuf migration path
 - [Benchmarks](/docs/benchmarks) — apples-to-apples vs. classical alternatives

76 lines 4.5 KiB Plaintext Raw Permalink Blame History

76 lines

4.5 KiB

Plaintext

Raw Permalink Blame History