The gRPC Data Stream Routing Layer exposes the data fabric's partition-routed streaming model over gRPC. Clients request a stream by naming a provider group and a partition key. The system uses a consistent hash ring to route the request directly to the node holding that partition — no broker or proxy in the hot path.
A named collection of nodes that together serve a stream type, e.g. "camera-feed". All nodes in the group share a common hash ring stored in NATS KV.
Each phase: write failing test, minimal code to pass, refactor. No production code without a red test first.
Date: 2026-03-09
Parent design: webrtc-playback-design.md
Test framework: testify (matches existing codebase)
Test location: cloud/video-service/internal/webrtc/*_test.go
This architecture replaces the standard Dapr Configuration Store component with a custom, high-performance Go SDK. It enables dynamic, partitioned processing of large configuration lists across a cluster of Go workers.
CockroachDB (CRDB) serves as the strict System of Record (SoR). To ensure security and decoupling, Go worker nodes possess zero database access. All configuration state, cluster topology, and event signaling are routed exclusively through NATS (JetStream, KV, and Core Request/Reply). The client SDK exposes an API identical to github.com/dapr/go-sdk/client to minimize developer friction.
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Pepper PRD — Product Requirements at a Glance</title> | |
| <style> | |
| * { box-sizing: border-box; margin: 0; padding: 0; } | |
| body { font-family: 'Segoe UI', system-ui, sans-serif; background: #080d14; color: #e2e8f0; min-height: 100vh; } |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Pepper Product Spec — Visual Overview</title> | |
| <style> | |
| * { box-sizing: border-box; margin: 0; padding: 0; } | |
| body { font-family: 'Segoe UI', system-ui, sans-serif; background: #07111e; color: #e2e8f0; } |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Pepper Feasibility Analysis — Visual Summary</title> | |
| <style> | |
| * { box-sizing: border-box; margin: 0; padding: 0; } | |
| body { font-family: 'Segoe UI', system-ui, sans-serif; background: #07101a; color: #e2e8f0; } |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Pepper — App Landscape Research Visual</title> | |
| <style> | |
| * { box-sizing: border-box; margin: 0; padding: 0; } | |
| body { font-family: 'Segoe UI', system-ui, sans-serif; background: #080c14; color: #e2e8f0; } |